{"push_id":825333207,"size":501,"distinct_size":0,"ref":"refs/heads/caf/ubifs/infradead.org/master","head":"1cb8f9776c7dcadc57885c6653943511d282633b","before":"7c7feb2ebfc9c0552c51f0c050db1d1a004faac5","commits":[{"sha":"ca9f26a27949ba3b295e4f0841c0bec9ef440141","author":{"email":"e38c087ad75d02f7b913a99f43aafdbb8740d800@mediatek.com","name":"Leilk Liu"},"message":"spi: mediatek: remove clk_disable_unprepare()\n\nThis patch removes clk_disable_unprepare() in mtk_spi_remove().\nclk_disable_prepare/unprepare must be balance, spi-clk is disabled\nin mtk_spi_probe, so not needs to disable again.\n\nSigned-off-by: Leilk Liu <leilk.liu@mediatek.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/ca9f26a27949ba3b295e4f0841c0bec9ef440141"},{"sha":"adcbcfea15d62fab5ba40ac28f9d2a590cc5e5e8","author":{"email":"e38c087ad75d02f7b913a99f43aafdbb8740d800@mediatek.com","name":"Leilk Liu"},"message":"spi: mediatek: fix spi clock usage error\n\nspi clock manages flow:\n  CLK_TOP_SYSPLL3_D2 ---> CLK_TOP_SPI_SEL ---> CLK_PERI_SPI0\n     (source clock)           (clock mux)       (clock gate)\nspi driver should choose source clock by clock mux, then enable\nclock gate.\n\nSigned-off-by: Leilk Liu <leilk.liu@mediatek.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/adcbcfea15d62fab5ba40ac28f9d2a590cc5e5e8"},{"sha":"3d4fe182003bcde778e29e84c14c0c4bb70a452e","author":{"email":"e38c087ad75d02f7b913a99f43aafdbb8740d800@mediatek.com","name":"Leilk Liu"},"message":"spi: Mediatek: Document devicetree bindings update for spi bus\n\nThis patch updates spi bindings, fixs clock usage description.\n\nSigned-off-by: Leilk Liu <leilk.liu@mediatek.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/3d4fe182003bcde778e29e84c14c0c4bb70a452e"},{"sha":"6bd3c6f75e0f9baddbf1196a7e3fceabb50c7e3c","author":{"email":"1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@maciej.szmigiero.name","name":"Maciej S. Szmigiero"},"message":"ASoC: fsl-asoc-card: put ASRC OF node in case of unknown device\n\nIn case of unknown DT compatible device the ASRC OF node\npossibly acquired earlier by of_parse_phandle() has\nto be put before returning from probe method.\n\nSigned-off-by: Maciej Szmigiero <mail@maciej.szmigiero.name>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/6bd3c6f75e0f9baddbf1196a7e3fceabb50c7e3c"},{"sha":"d76f41982f2fc88492efd96c7c3178044f32e125","author":{"email":"5d78902c885bda21bab1f3f4d20718dff0167f20@gmail.com","name":"Anatol Pomozov"},"message":"ASoC: Document snd-soc-dummy-dai purpose\n\nSigned-off-by: Anatol Pomozov <anatol.pomozov@gmail.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/d76f41982f2fc88492efd96c7c3178044f32e125"},{"sha":"51d2eeef1d958ef6834b24f548194f5acea0f499","author":{"email":"551ae05ce198473af5b9da594240f54df5f81e31@gmail.com","name":"Sudip Mukherjee"},"message":"ASoC: wm0010: fix memory leak\n\nWe were aborting if the kzalloc of img_swap fails but without freeing the\nalready allocated out. Similarly we were aborting if spi_sync fails\nwithout releasing out and img_swap.\n\nSigned-off-by: Sudip Mukherjee <sudip@vectorindia.org>\nAcked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/51d2eeef1d958ef6834b24f548194f5acea0f499"},{"sha":"fe8291e82b5d0b79b743683e5c0fb7e273f7a99a","author":{"email":"bfa0a1520768723a1c60e18250fb841c342eb8d8@ti.com","name":"Grygorii Strashko"},"message":"ARM: OMAP2+: omap-device: fix race deferred probe of omap_hsmmc vs omap_device_late_init\n\nKernel fails to boot 50% of times (form build to build) with\nRT-patchset applied due to the following race - on late boot\nstages deferred_probe_work_func->omap_hsmmc_probe races with omap_device_late_ini.\n\nThe same issue has been reported now on linux-next (4.3) by Keerthy [1]\n\nlate_initcall\n - deferred_probe_initcal() tries to re-probe all pending driver's probe.\n\n- later on, some driver is probing in this case It's cpsw.c\n  (but could be any other drivers)\n  cpsw_init\n  - platform_driver_register\n    - really_probe\n       - driver_bound\n         - driver_deferred_probe_trigger\n  and boot proceed.\n  So, at this moment we have deferred_probe_work_func scheduled.\n\nlate_initcall_sync\n  - omap_device_late_init\n    - omap_device_idle\n\nCPU1\t\t\t\t\tCPU2\n  - deferred_probe_work_func\n    - really_probe\n      - omap_hsmmc_probe\n\t- pm_runtime_get_sync\n\t\t\t\t\tlate_initcall_sync\n\t\t\t\t\t- omap_device_late_init\n\t\t\t\t\t\tif (od->_driver_status != BUS_NOTIFY_BOUND_DRIVER) {\n\t\t\t\t\t\t\tif (od->_state == OMAP_DEVICE_STATE_ENABLED) {\n\t\t\t\t\t\t\t\t- omap_device_idle [ops - IP is disabled]\n\t- [fail]\n\t- pm_runtime_put_sync\n          - omap_hsmmc_runtime_suspend [ooops!]\n\n== log ==\n omap_hsmmc 480b4000.mmc: unable to get vmmc regulator -517\n davinci_mdio 48485000.mdio: davinci mdio revision 1.6\n davinci_mdio 48485000.mdio: detected phy mask fffffff3\n libphy: 48485000.mdio: probed\n davinci_mdio 48485000.mdio: phy[2]: device 48485000.mdio:02, driver unknown\n davinci_mdio 48485000.mdio: phy[3]: device 48485000.mdio:03, driver unknown\n omap_hsmmc 480b4000.mmc: unable to get vmmc regulator -517\n cpsw 48484000.ethernet: Detected MACID = b4:99:4c:c7:d2:48\n cpsw 48484000.ethernet: cpsw: Detected MACID = b4:99:4c:c7:d2:49\n hctosys: unable to open rtc device (rtc0)\n omap_hsmmc 480b4000.mmc: omap_device_late_idle: enabled but no driver.  Idling\n ldousb: disabling\n Unhandled fault: imprecise external abort (0x1406) at 0x00000000\n [00000000] *pgd=00000000\n Internal error: : 1406 [#1] PREEMPT SMP ARM\n Modules linked in:\n CPU: 1 PID: 58 Comm: kworker/u4:1 Not tainted 4.1.2-rt1-00467-g6da3c0a-dirty #5\n Hardware name: Generic DRA74X (Flattened Device Tree)\n Workqueue: deferwq deferred_probe_work_func\n task: ee6ddb00 ti: edd3c000 task.ti: edd3c000\n PC is at omap_hsmmc_runtime_suspend+0x1c/0x12c\n LR is at _od_runtime_suspend+0xc/0x24\n pc : [<c0471998>]    lr : [<c0029590>]    psr: a0000013\n sp : edd3dda0  ip : ee6ddb00  fp : c07be540\n r10: 00000000  r9 : c07be540  r8 : 00000008\n r7 : 00000000  r6 : ee646c10  r5 : ee646c10  r4 : edd79380\n r3 : fa0b4100  r2 : 00000000  r1 : 00000000  r0 : ee646c10\n Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel\n Control: 10c5387d  Table: 8000406a  DAC: 00000015\n Process kworker/u4:1 (pid: 58, stack limit = 0xedd3c218)\n Stack: (0xedd3dda0 to 0xedd3e000)\n dda0: ee646c70 ee646c10 c0029584 00000000 00000008 c0029590 ee646c70 ee646c10\n ddc0: c0029584 c03adfb8 ee646c10 00000004 0000000c c03adff0 ee646c10 00000004\n dde0: 0000000c c03ae4ec 00000000 edd3c000 ee646c10 00000004 ee646c70 00000004\n de00: fa0b4000 c03aec20 ee6ddb00 ee646c10 00000004 ee646c70 ee646c10 fffffdfb\n de20: edd79380 00000000 fa0b4000 c03aee90 fffffdfb edd79000 ee646c00 c0474290\n de40: 00000000 edda24c0 edd79380 edc81f00 00000000 00000200 00000001 c06dd488\n de60: edda3960 ee646c10 ee646c10 c0824cc4 fffffdfb c0880c94 00000002 edc92600\n de80: c0836378 c03a7f84 ee646c10 c0824cc4 00000000 c0880c80 c0880c94 c03a6568\n dea0: 00000000 ee646c10 c03a66ac ee4f8000 00000000 00000001 edc92600 c03a4b40\n dec0: ee404c94 edc83c4c ee646c10 ee646c10 ee646c44 c03a63c4 ee646c10 ee646c10\n dee0: c0814448 c03a5aa8 ee646c10 c0814220 edd3c000 c03a5ec0 c0814250 ee6be400\n df00: edd3c000 c004e5bc ee6ddb01 00000078 ee6ddb00 ee4f8000 ee6be418 edd3c000\n df20: ee4f8028 00000088 c0836045 ee4f8000 ee6be400 c004e928 ee4f8028 00000000\n df40: c004e8ec 00000000 ee6bf1c0 ee6be400 c004e8ec 00000000 00000000 00000000\n df60: 00000000 c0053450 2e56fa97 00000000 afdffbd7 ee6be400 00000000 00000000\n df80: edd3df80 edd3df80 00000000 00000000 edd3df90 edd3df90 edd3dfac ee6bf1c0\n dfa0: c0053384 00000000 00000000 c000f668 00000000 00000000 00000000 00000000\n dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000\n dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 f1fc9d7e febfbdff\n [<c0471998>] (omap_hsmmc_runtime_suspend) from [<c0029590>] (_od_runtime_suspend+0xc/0x24)\n [<c0029590>] (_od_runtime_suspend) from [<c03adfb8>] (__rpm_callback+0x24/0x3c)\n [<c03adfb8>] (__rpm_callback) from [<c03adff0>] (rpm_callback+0x20/0x80)\n [<c03adff0>] (rpm_callback) from [<c03ae4ec>] (rpm_suspend+0xe4/0x618)\n [<c03ae4ec>] (rpm_suspend) from [<c03aee90>] (__pm_runtime_idle+0x60/0x80)\n [<c03aee90>] (__pm_runtime_idle) from [<c0474290>] (omap_hsmmc_probe+0x6bc/0xa7c)\n [<c0474290>] (omap_hsmmc_probe) from [<c03a7f84>] (platform_drv_probe+0x44/0xa4)\n [<c03a7f84>] (platform_drv_probe) from [<c03a6568>] (driver_probe_device+0x170/0x2b4)\n [<c03a6568>] (driver_probe_device) from [<c03a4b40>] (bus_for_each_drv+0x64/0x98)\n [<c03a4b40>] (bus_for_each_drv) from [<c03a63c4>] (device_attach+0x70/0x88)\n [<c03a63c4>] (device_attach) from [<c03a5aa8>] (bus_probe_device+0x84/0xac)\n [<c03a5aa8>] (bus_probe_device) from [<c03a5ec0>] (deferred_probe_work_func+0x58/0x88)\n [<c03a5ec0>] (deferred_probe_work_func) from [<c004e5bc>] (process_one_work+0x134/0x464)\n [<c004e5bc>] (process_one_work) from [<c004e928>] (worker_thread+0x3c/0x4fc)\n [<c004e928>] (worker_thread) from [<c0053450>] (kthread+0xcc/0xe4)\n [<c0053450>] (kthread) from [<c000f668>] (ret_from_fork+0x14/0x2c)\n Code: e594302c e593202c e584205c e594302c (e5932128)\n ---[ end trace 0000000000000002 ]---\n\nThe issue happens because omap_device_late_init() do not take into\naccount that some drivers are present, but their probes were not\nfinished successfully and where deferred instead. This is the valid\ncase, and omap_device_late_init() should not idle such devices.\n\nTo fix this issue, the value of omap_device->_driver_status field\nshould be checked not only for BUS_NOTIFY_BOUND_DRIVER (driver is\npresent and has been bound to device successfully), but also checked\nfor BUS_NOTIFY_BIND_DRIVER (driver about to be bound) - which means\ndriver is present and there was try to bind it to device.\n\n[1] http://www.spinics.net/lists/arm-kernel/msg441880.html\nCc: Tero Kristo <t-kristo@ti.com>\nCc: Keerthy <j-keerthy@ti.com>\nTested-by: Keerthy <j-keerthy@ti.com>\nSigned-off-by: Grygorii Strashko <grygorii.strashko@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/fe8291e82b5d0b79b743683e5c0fb7e273f7a99a"},{"sha":"874b300a6a0bfe97225ed1f8648fa92238e4d9e9","author":{"email":"1001e8702733cced254345e193c88aaa47a4f5de@atomide.com","name":"Tony Lindgren"},"message":"ARM: OMAP2+: Fix booting if no timer parent clock is available\n\nWhen bringing up a new SoC we needlessly prevent booting at timer\ninit if timer clock_set_parent fails. This can fail if the system\nis booting on bootloader configured PLL values until the clock\nframework driver for the PLL is implemented.\n\nLet's just WARN instead, this will provide helpful information\nfor anybody bringing up a new SoC what needs to be fixed.\n\nThis allows to boot dm814x that's still missing the PLL driver.\n\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/874b300a6a0bfe97225ed1f8648fa92238e4d9e9"},{"sha":"05f4f1abc274ac7e8e83424d0cef2d842db91815","author":{"email":"4cc5f7dfc6b9453b73d1fba73a574c3df56fb76e@gmail.com","name":"Frans Klaver"},"message":"ARM: OMAP3: vc: fix 'or' always true warning\n\nFix the warning:\narch/arm/mach-omap2/vc.c:302:47: warning: logical ‘or’ of collectively exhaustive tests is always true [-Wlogical-op]\n\nAs we're toggling both CLKREQ and OFFMODE, we should also be checking\nOFFMODE.\n\nSigned-off-by: Frans Klaver <fransklaver@gmail.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/05f4f1abc274ac7e8e83424d0cef2d842db91815"},{"sha":"81032e34e184a8d63598d215a6d4a3352018ffea","author":{"email":"9c93b0ec5c7dacd10ea50ed05a8fa5f367b92846@ti.com","name":"Vishal Mahaveer"},"message":"ARM: DRA752: Add ID detect for ES2.0\n\nES2.0 is a minor variant of ES1.1. ES2.0 is an incremental revision\nwith various fixes including the following:\n\t- reset logic fixes\n\t- few assymetric aging logic fixes\n\t- MMC clock rate fixes\n\t- Ethernet speed fixes\n\t- edma fixes for mcasp\n\nNOTE: even though we use a compatible of dra742 and dra752, the usage in\nthe Linux kernel is more or less interchangable - we use dra752 more\noften in the linux kernel compared to dra742 and 4.2-rc6\n\nSigned-off-by: Vishal Mahaveer <vishalm@ti.com>\nSigned-off-by: Nishanth Menon <nm@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/81032e34e184a8d63598d215a6d4a3352018ffea"},{"sha":"21b430d23d233c67e6589ea5054d18392e15a28e","author":{"email":"1001e8702733cced254345e193c88aaa47a4f5de@atomide.com","name":"Tony Lindgren"},"message":"ARM: omap2plus_defconfig: Enable MUSB DMA support\n\nWith recent MUSB changes we can now build in support for multiple\nDMA implementations. So let's enable DMA by default to make life\neasier for distro use.\n\nAcked-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/21b430d23d233c67e6589ea5054d18392e15a28e"},{"sha":"02bc933ebb59208f42c2e6305b2c17fd306f695d","author":{"email":"c234c463242bf468d87712cfa6b4608827c927f9@intel.com","name":"Tan, Jui Nee"},"message":"spi: spi-pxa2xx: Check status register to determine if SSSR_TINT is disabled\n\nOn Intel Baytrail, there is case when interrupt handler get called, no SPI\nmessage is captured. The RX FIFO is indeed empty when RX timeout pending\ninterrupt (SSSR_TINT) happens.\n\nUse the BIOS version where both HSUART and SPI are on the same IRQ. Both\ndrivers are using IRQF_SHARED when calling the request_irq function. When\nrunning two separate and independent SPI and HSUART application that\ngenerate data traffic on both components, user will see messages like\nbelow on the console:\n\n  pxa2xx-spi pxa2xx-spi.0: bad message state in interrupt handler\n\nThis commit will fix this by first checking Receiver Time-out Interrupt,\nif it is disabled, ignore the request and return without servicing.\n\nSigned-off-by: Tan, Jui Nee <jui.nee.tan@intel.com>\nAcked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/02bc933ebb59208f42c2e6305b2c17fd306f695d"},{"sha":"9f8df6adf6c53abfa10e243cb289c34eb18ec581","author":{"email":"551ae05ce198473af5b9da594240f54df5f81e31@gmail.com","name":"Sudip Mukherjee"},"message":"regulator: core: fix possible NULL dereference\n\nWe were checking rdev->supply for NULL after dereferencing it. Lets\ncheck for rdev->supply along with _regulator_is_enabled() and call\nregulator_enable() only if rdev->supply is not NULL.\n\nSigned-off-by: Sudip Mukherjee <sudip@vectorindia.org>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/9f8df6adf6c53abfa10e243cb289c34eb18ec581"},{"sha":"b9c93646fd5cb669d096fec5ad25a01f04cfde27","author":{"email":"c224db9378a929ae8338a052bbb1b30fb46cdd39@ti.com","name":"Kishon Vijay Abraham I"},"message":"regulator: pbias: program pbias register offset in pbias driver\n\nAdd separate compatible strings for every platform and populate the\npbias register offset in the driver data.\nThis helps avoid depending on the dt for pbias register offset.\n\nAlso update the dt binding documentation for the new compatible\nstrings.\n\nSuggested-by: Tony Lindgren <tony@atomide.com>\nSigned-off-by: Kishon Vijay Abraham I <kishon@ti.com>\nAcked-by: Tony Lindgren <tony@atomide.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/b9c93646fd5cb669d096fec5ad25a01f04cfde27"},{"sha":"a394d635193b641f2c86ead5ada5b115d57c51f8","author":{"email":"ba324ca7b1c77fc20bb970d5aff6eea9377918a5@roeck-us.net","name":"Guenter Roeck"},"message":"spi: Fix documentation of spi_alloc_master()\n\nActually, spi_master_put() after spi_alloc_master() must _not_ be followed\nby kfree(). The memory is already freed with the call to spi_master_put()\nthrough spi_master_class, which registers a release function. Calling both\nspi_master_put() and kfree() results in often nasty (and delayed) crashes\nelsewhere in the kernel, often in the networking stack.\n\nThis reverts commit eb4af0f5349235df2e4a5057a72fc8962d00308a.\n\nLink to patch and concerns: https://lkml.org/lkml/2012/9/3/269\nor\nhttp://lkml.iu.edu/hypermail/linux/kernel/1209.0/00790.html\n\nAlexey Klimov: This revert becomes valid after\n94c69f765f1b4a658d96905ec59928e3e3e07e6a when spi-imx.c\nhas been fixed and there is no need to call kfree() so comment\nfor spi_alloc_master() should be fixed.\n\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Alexey Klimov <alexey.klimov@linaro.org>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/a394d635193b641f2c86ead5ada5b115d57c51f8"},{"sha":"6583d2032d57df9f1c00c753ca58e1a822901bf0","author":{"email":"e38c087ad75d02f7b913a99f43aafdbb8740d800@mediatek.com","name":"Leilk Liu"},"message":"spi: mediatek: fix spi cs polarity error\n\nMediatek spi HW can't set cs inactive(keep cs high) directly.\nInstead, it supplies pause mode to do it indirectly. If driver\nunsets SPI_CMD_PAUSE_MODE in CMD_REG, it also needs to reset\ninternal state machine to let cs inactive at once.\n\nSigned-off-by: Leilk Liu <leilk.liu@mediatek.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/6583d2032d57df9f1c00c753ca58e1a822901bf0"},{"sha":"6af3e3adcac595a683bb55299a907d7d1ad61ab3","author":{"email":"e0fcd583df77ec6c08e6d1257619cc1216ddc994@suse.com","name":"Filipe Manana"},"message":"Btrfs: don't initialize a space info as full to prevent ENOSPC\n\nCommit 2e6e518335f8 (\"Btrfs: fix block group ->space_info null pointer\ndereference\") accidently marked a space info as full when initializing\nit with a value of 0 total bytes. This introduces an ENOSPC problem when\nwriting file data if we mount a filesystem that has no data block groups\nallocated, because the data space info is initialized with 0 total bytes,\nmarked as full, and it never gets its total bytes incremented by a\n(positive) value to unmark it as full (because there are no data block\ngroups loaded when the fs is mounted).\nFor metadata and system spaces this issue can never happen since we always\nhave at least one metadata block group and one system block group (even\nfor an empty filesystem).\n\nSo fix this by just not initializing a space info as full, reverting the\noffending part of the commit mentioned above.\n\nThe following test case for fstests reproduces the issue:\n\n  seq=`basename $0`\n  seqres=$RESULT_DIR/$seq\n  echo \"QA output created by $seq\"\n  tmp=/tmp/$$\n  status=1\t# failure is the default!\n  trap \"_cleanup; exit \\$status\" 0 1 2 3 15\n\n  _cleanup()\n  {\n      rm -f $tmp.*\n  }\n\n  # get standard environment, filters and checks\n  . ./common/rc\n  . ./common/filter\n\n  # real QA test starts here\n  _need_to_be_root\n  _supported_fs btrfs\n  _supported_os Linux\n  _require_scratch\n\n  rm -f $seqres.full\n\n  _scratch_mkfs >>$seqres.full 2>&1\n\n  # Mount our filesystem without space caches enabled so that we do not\n  # get any space used from the initial data block group that mkfs creates\n  # (space caches used space from data block groups).\n  _scratch_mount \"-o nospace_cache\"\n\n  # Need an fs with at least 2Gb to make sure mkfs.btrfs does not create\n  # an fs using mixed block groups (used both for data and metadata). We\n  # really need to have dedicated block groups for data to reproduce the\n  # issue and mkfs.btrfs defaults to mixed block groups only for small\n  # filesystems (up to 1Gb).\n  _require_fs_space $SCRATCH_MNT $((2 * 1024 * 1024))\n\n  # Run balance with the purpose of deleting the unused data block group\n  # that mkfs created. We could also wait for the background kthread to\n  # automatically delete the unused block group, but we do not have a way\n  # to make it run and wait for it to complete, so just do a balance\n  # instead of some unreliable sleep\n  _run_btrfs_util_prog balance start -dusage=0 $SCRATCH_MNT\n\n  # Now unmount the filesystem, mount it again (either with or with space\n  # caches enabled, it does not matter to trigger the problem) and attempt\n  # to create a file with some data - this used to fail with ENOSPC\n  # because there were no data block groups when the filesystem was\n  # mounted and the data space info object was marked as full when\n  # initialized (because it had 0 total bytes), which prevented the file\n  # write path from attempting to allocate a data block group and fail\n  # immediately with ENOSPC.\n  _scratch_remount\n  echo \"hello world\" > $SCRATCH_MNT/foobar\n\n  echo \"Silence is golden\"\n  status=0\n  exit\n\nSigned-off-by: Filipe Manana <fdmanana@suse.com>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/6af3e3adcac595a683bb55299a907d7d1ad61ab3"},{"sha":"721b51fcf91898299d96f4b72cb9434cda29dce6","author":{"email":"8a81b8566f52dcc2bf003ea1ff66de336523b474@realtek.com","name":"John Lin"},"message":"ASoC: rt5645: Add struct dmi_system_id \"Google Ultima\" for chrome platform\n\nSigned-off-by: John Lin <john.lin@realtek.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/721b51fcf91898299d96f4b72cb9434cda29dce6"},{"sha":"f1ec5ec7a94ba8138f9cbdc1e9e3b03aee29c4df","author":{"email":"1c687ae09fa7f11acd34075a0ae6b39df2be9341@linux.intel.com","name":"Liam Girdwood"},"message":"ASoC: intel: Fix SSP port configuration after RTD3 resume.\n\nCurrently the SSP port settings are being clobbered as part of the DSP\nRTD3 restore logic. make sure we save the correct params and restore them\nat resume. The FW sadly does not save SSP settings as part of the PM\ncontext.\n\nSigned-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/f1ec5ec7a94ba8138f9cbdc1e9e3b03aee29c4df"},{"sha":"2a3fffd45822070309bcf0b1e1dae624d633824a","author":{"email":"c65a0fb7e74ffd2c9fc3a0f9aacb0f6a24b0a68b@martin.sperl.org","name":"Martin Sperl"},"message":"spi: bcm2835: BUG: fix wrong use of PAGE_MASK\n\nThere is a bug in the alignment checking of transfers,\nthat results in DMA not being used for un-aligned\ntransfers that do not cross page-boundries, which is valid.\n\nThis is due to a missconception of the meaning PAGE_MASK\nwhen implementing that check originally - (PAGE_SIZE - 1)\nshould have been used instead.\n\nAlso fixes a copy/paste error.\n\nReported-by: <robert@axium.co.nz>\nSigned-off-by: Martin Sperl <kernel@martin.sperl.org>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/MSM8916-Samsung/kernel_msm-3.10/commits/2a3fffd45822070309bcf0b1e1dae624d633824a"}]}