{"push_id":1374823813,"size":137,"distinct_size":1,"ref":"refs/heads/lambda-devel","head":"f252f0aaa0f9ab53e2d5e18b616f699e184a32f3","before":"73eba5e312a8e483776e92e930b79f6409ecf7e6","commits":[{"sha":"f823e03be34a9f0049218784d0f3df353b2dbdfd","author":{"name":"Johannes Berg","email":"9a5936d824e6835dfe162c5611d10d2cf40ffbad@intel.com"},"message":"mac80211: fix driver RSSI event calculations\n\ncommit 8ec6d97871f37e4743678ea4a455bd59580aa0f4 upstream.\n\nThe ifmgd->ave_beacon_signal value cannot be taken as is for\ncomparisons, it must be divided by since it's represented\nlike that for better accuracy of the EWMA calculations. This\nwould lead to invalid driver RSSI events. Fix the used value.\n\nFixes: 615f7b9bb1f8 (\"mac80211: add driver RSSI threshold events\")\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/f823e03be34a9f0049218784d0f3df353b2dbdfd"},{"sha":"d1aee82a3672a5ebef47f3c26efee131d404c1e2","author":{"name":"Valentin Rothberg","email":"3f13aee75994c4502e40623b49761435eef81a56@gmail.com"},"message":"wm831x_power: Use IRQF_ONESHOT to request threaded IRQs\n\ncommit 90adf98d9530054b8e665ba5a928de4307231d84 upstream.\n\nSince commit 1c6c69525b40 (\"genirq: Reject bogus threaded irq requests\")\nthreaded IRQs without a primary handler need to be requested with\nIRQF_ONESHOT, otherwise the request will fail.\n\nscripts/coccinelle/misc/irqf_oneshot.cocci detected this issue.\n\nFixes: b5874f33bbaf (\"wm831x_power: Use genirq\")\nSigned-off-by: Valentin Rothberg <valentinrothberg@gmail.com>\nSigned-off-by: Sebastian Reichel <sre@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/d1aee82a3672a5ebef47f3c26efee131d404c1e2"},{"sha":"f2cecea596dad967975926f4ad85f560d27c70ff","author":{"name":"Dan Carpenter","email":"60b2bf2bc0bec4ca4a4b046ca7ef9255248abff8@oracle.com"},"message":"mwifiex: fix mwifiex_rdeeprom_read()\n\ncommit 1f9c6e1bc1ba5f8a10fcd6e99d170954d7c6d382 upstream.\n\nThere were several bugs here.\n\n1)  The done label was in the wrong place so we didn't copy any\n    information out when there was no command given.\n\n2)  We were using PAGE_SIZE as the size of the buffer instead of\n    \"PAGE_SIZE - pos\".\n\n3)  snprintf() returns the number of characters that would have been\n    printed if there were enough space.  If there was not enough space\n    (and we had fixed the memory corruption bug #2) then it would result\n    in an information leak when we do simple_read_from_buffer().  I've\n    changed it to use scnprintf() instead.\n\nI also removed the initialization at the start of the function, because\nI thought it made the code a little more clear.\n\nFixes: 5e6e3a92b9a4 ('wireless: mwifiex: initial commit for Marvell mwifiex driver')\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nAcked-by: Amitkumar Karwar <akarwar@marvell.com>\nSigned-off-by: Kalle Valo <kvalo@codeaurora.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/f2cecea596dad967975926f4ad85f560d27c70ff"},{"sha":"f3a5c852adb3c702cd3772dc3bbb0d8e7a599643","author":{"name":"Dan Carpenter","email":"60b2bf2bc0bec4ca4a4b046ca7ef9255248abff8@oracle.com"},"message":"devres: fix a for loop bounds check\n\ncommit 1f35d04a02a652f14566f875aef3a6f2af4cb77b upstream.\n\nThe iomap[] array has PCIM_IOMAP_MAX (6) elements and not\nDEVICE_COUNT_RESOURCE (16).  This bug was found using a static checker.\nIt may be that the \"if (!(mask & (1 << i)))\" check means we never\nactually go past the end of the array in real life.\n\nFixes: ec04b075843d ('iomap: implement pcim_iounmap_regions()')\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nAcked-by: Tejun Heo <tj@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/f3a5c852adb3c702cd3772dc3bbb0d8e7a599643"},{"sha":"0f4d89a8c7a1c2e11ac765efcd9a0c90dcaeeff7","author":{"name":"Arnd Bergmann","email":"72a0f6d3b182607e6d5c44b93e1abb7b23ee18f3@arndb.de"},"message":"ARM: pxa: remove incorrect __init annotation on pxa27x_set_pwrmode\n\ncommit 54c09889bff6d99c8733eed4a26c9391b177c88b upstream.\n\nThe z2 machine calls pxa27x_set_pwrmode() in order to power off\nthe machine, but this function gets discarded early at boot because\nit is marked __init, as pointed out by kbuild:\n\nWARNING: vmlinux.o(.text+0x145c4): Section mismatch in reference from the function z2_power_off() to the function .init.text:pxa27x_set_pwrmode()\nThe function z2_power_off() references\nthe function __init pxa27x_set_pwrmode().\nThis is often because z2_power_off lacks a __init\nannotation or the annotation of pxa27x_set_pwrmode is wrong.\n\nThis removes the __init section modifier to fix rebooting and the\nbuild error.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nFixes: ba4a90a6d86a (\"ARM: pxa/z2: fix building error of pxa27x_cpu_suspend() no longer available\")\nSigned-off-by: Robert Jarzmik <robert.jarzmik@free.fr>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/0f4d89a8c7a1c2e11ac765efcd9a0c90dcaeeff7"},{"sha":"bec31ecff6da8684ec171747bf95b57d4973cdae","author":{"name":"Ralf Baechle","email":"e34dc0f431cfd5378400841df3658f4880373a71@linux-mips.org"},"message":"MIPS: atomic: Fix comment describing atomic64_add_unless's return value.\n\ncommit f25319d2cb439249a6859f53ad42ffa332b0acba upstream.\n\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nFixes: f24219b4e90cf70ec4a211b17fbabc725a0ddf3c\n(cherry picked from commit f0a232cde7be18a207fd057dd79bbac8a0a45dec)\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/bec31ecff6da8684ec171747bf95b57d4973cdae"},{"sha":"412339444022ecde3940501de66aab4dafc9a8a5","author":{"name":"libin","email":"22b0b1264d7a67107b5064e55d2ce92d5086527b@huawei.com"},"message":"recordmcount: Fix endianness handling bug for nop_mcount\n\ncommit c84da8b9ad3761eef43811181c7e896e9834b26b upstream.\n\nIn nop_mcount, shdr->sh_offset and welp->r_offset should handle\nendianness properly, otherwise it will trigger Segmentation fault\nif the recordmcount main and file.o have different endianness.\n\nLink: http://lkml.kernel.org/r/563806C7.7070606@huawei.com\n\nSigned-off-by: Li Bin <huawei.libin@huawei.com>\nSigned-off-by: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/412339444022ecde3940501de66aab4dafc9a8a5"},{"sha":"e46ce755784262a76624c9f8e2f23c8e252c827b","author":{"name":"Michal Kubeček","email":"47170cf003259559754eb8c2b060d5264f7a71b5@suse.cz"},"message":"ipv6: fix tunnel error handling\n\ncommit ebac62fe3d24c0ce22dd83afa7b07d1a2aaef44d upstream.\n\nBoth tunnel6_protocol and tunnel46_protocol share the same error\nhandler, tunnel6_err(), which traverses through tunnel6_handlers list.\nFor ipip6 tunnels, we need to traverse tunnel46_handlers as we do e.g.\nin tunnel46_rcv(). Current code can generate an ICMPv6 error message\nwith an IPv4 packet embedded in it.\n\nFixes: 73d605d1abbd (\"[IPSEC]: changing API of xfrm6_tunnel_register\")\nSigned-off-by: Michal Kubecek <mkubecek@suse.cz>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/e46ce755784262a76624c9f8e2f23c8e252c827b"},{"sha":"de6889ac8e15b2b9f6a3ce98e64ffb2b6c583e68","author":{"name":"Christoph Hellwig","email":"ed9f47d6dfaca04b245b5f2816a0d3e9462a0b83@lst.de"},"message":"scsi: restart list search after unlock in scsi_remove_target\n\ncommit 40998193560dab6c3ce8d25f4fa58a23e252ef38 upstream.\n\nWhen dropping a lock while iterating a list we must restart the search\nas other threads could have manipulated the list under us.  Without this\nwe can get stuck in an endless loop.  This bug was introduced by\n\ncommit bc3f02a795d3b4faa99d37390174be2a75d091bd\nAuthor: Dan Williams <djbw@fb.com>\nDate:   Tue Aug 28 22:12:10 2012 -0700\n\n    [SCSI] scsi_remove_target: fix softlockup regression on hot remove\n\nWhich was itself trying to fix a reported soft lockup issue\n\nhttp://thread.gmane.org/gmane.linux.kernel/1348679\n\nHowever, we believe even with this revert of the original patch, the soft\nlockup problem has been fixed by\n\ncommit f2495e228fce9f9cec84367547813cbb0d6db15a\nAuthor: James Bottomley <JBottomley@Parallels.com>\nDate:   Tue Jan 21 07:01:41 2014 -0800\n\n    [SCSI] dual scan thread bug fix\n\nThanks go to Dan Williams <dan.j.williams@intel.com> for tracking all this\nprior history down.\n\nReported-by: Johannes Thumshirn <jthumshirn@suse.de>\nSigned-off-by: Christoph Hellwig <hch@lst.de>\nTested-by: Johannes Thumshirn <jthumshirn@suse.de>\nReviewed-by: Johannes Thumshirn <jthumshirn@suse.de>\nFixes: bc3f02a795d3b4faa99d37390174be2a75d091bd\nSigned-off-by: James Bottomley <JBottomley@Odin.com>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/de6889ac8e15b2b9f6a3ce98e64ffb2b6c583e68"},{"sha":"e3ef444ebfe39cb7f395abfcd79b8d5868fe8172","author":{"name":"Eric Dumazet","email":"b3d77ad2db30f558882cc0c038be5a3cf96611f9@google.com"},"message":"net: fix a race in dst_release()\n\ncommit d69bbf88c8d0b367cf3e3a052f6daadf630ee566 upstream.\n\nOnly cpu seeing dst refcount going to 0 can safely\ndereference dst->flags.\n\nOtherwise an other cpu might already have freed the dst.\n\nFixes: 27b75c95f10d (\"net: avoid RCU for NOCACHE dst\")\nReported-by: Greg Thelen <gthelen@google.com>\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/e3ef444ebfe39cb7f395abfcd79b8d5868fe8172"},{"sha":"12106350e316620fc012971fab93e29040c7bfcb","author":{"name":"Kinglong Mee","email":"edb7e4e38dad4b3954adaa5ef0528f2414afae6a@gmail.com"},"message":"FS-Cache: Increase reference of parent after registering, netfs success\n\ncommit 86108c2e34a26e4bec3c6ddb23390bf8cedcf391 upstream.\n\nIf netfs exist, fscache should not increase the reference of parent's\nusage and n_children, otherwise, never be decreased.\n\nv2: thanks David's suggest,\n move increasing reference of parent if success\n use kmem_cache_free() freeing primary_index directly\n\nv3: don't move \"netfs->primary_index->parent = &fscache_fsdef_index;\"\n\nSigned-off-by: Kinglong Mee <kinglongmee@gmail.com>\nSigned-off-by: David Howells <dhowells@redhat.com>\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/12106350e316620fc012971fab93e29040c7bfcb"},{"sha":"d234c0f698e54cdc5713bbc975214050c3cf9389","author":{"name":"Kinglong Mee","email":"edb7e4e38dad4b3954adaa5ef0528f2414afae6a@gmail.com"},"message":"FS-Cache: Don't override netfs's primary_index if registering failed\n\ncommit b130ed5998e62879a66bad08931a2b5e832da95c upstream.\n\nOnly override netfs->primary_index when registering success.\n\nSigned-off-by: Kinglong Mee <kinglongmee@gmail.com>\nSigned-off-by: David Howells <dhowells@redhat.com>\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>\n[lizf: Backported to 3.4: there are no n_active and flags in primary_index]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/d234c0f698e54cdc5713bbc975214050c3cf9389"},{"sha":"253a4fa797bdadff7f6c96b8f9188bf0a415829c","author":{"name":"David Howells","email":"358fdf7bce8223edb2a0d846104bf62a286894d5@redhat.com"},"message":"FS-Cache: Handle a write to the page immediately beyond the EOF marker\n\ncommit 102f4d900c9c8f5ed89ae4746d493fe3ebd7ba64 upstream.\n\nHandle a write being requested to the page immediately beyond the EOF\nmarker on a cache object.  Currently this gets an assertion failure in\nCacheFiles because the EOF marker is used there to encode information about\na partial page at the EOF - which could lead to an unknown blank spot in\nthe file if we extend the file over it.\n\nThe problem is actually in fscache where we check the index of the page\nbeing written against store_limit.  store_limit is set to the number of\npages that we're allowed to store by fscache_set_store_limit() - which\nmeans it's one more than the index of the last page we're allowed to store.\nThe problem is that we permit writing to a page with an index _equal_ to\nthe store limit - when we should reject that case.\n\nWhilst we're at it, change the triggered assertion in CacheFiles to just\nreturn -ENOBUFS instead.\n\nThe assertion failure looks something like this:\n\nCacheFiles: Assertion failed\n1000 < 7b1 is false\n------------[ cut here ]------------\nkernel BUG at fs/cachefiles/rdwr.c:962!\n...\nRIP: 0010:[<ffffffffa02c9e83>]  [<ffffffffa02c9e83>] cachefiles_write_page+0x273/0x2d0 [cachefiles]\n\nSigned-off-by: David Howells <dhowells@redhat.com>\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/253a4fa797bdadff7f6c96b8f9188bf0a415829c"},{"sha":"7bc07836f031b3445da0e276176b4b84d7bbed3d","author":{"name":"Boris BREZILLON","email":"d3686c1eb756201cacdf5983212dc6c4a5a469fe@free-electrons.com"},"message":"mtd: mtdpart: fix add_mtd_partitions error path\n\ncommit e5bae86797141e4a95e42d825f737cb36d7b8c37 upstream.\n\nIf we fail to allocate a partition structure in the middle of the partition\ncreation process, the already allocated partitions are never removed, which\nmeans they are still present in the partition list and their resources are\nnever freed.\n\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Brian Norris <computersforpeace@gmail.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/7bc07836f031b3445da0e276176b4b84d7bbed3d"},{"sha":"428b68c783a12cc5517a49e549cd50c31d3b6d49","author":{"name":"David Woodhouse","email":"151db71fa574ba9de894f2e2d638da3ac90ff437@intel.com"},"message":"iommu/vt-d: Fix ATSR handling for Root-Complex integrated endpoints\n\ncommit d14053b3c714178525f22660e6aaf41263d00056 upstream.\n\nThe VT-d specification says that \"Software must enable ATS on endpoint\ndevices behind a Root Port only if the Root Port is reported as\nsupporting ATS transactions.\"\n\nWe walk up the tree to find a Root Port, but for integrated devices we\ndon't find one — we get to the host bridge. In that case we *should*\nallow ATS. Currently we don't, which means that we are incorrectly\nfailing to use ATS for the integrated graphics. Fix that.\n\nWe should never break out of this loop \"naturally\" with bus==NULL,\nsince we'll always find bridge==NULL in that case (and now return 1).\n\nSo remove the check for (!bridge) after the loop, since it can never\nhappen. If it did, it would be worthy of a BUG_ON(!bridge). But since\nit'll oops anyway in that case, that'll do just as well.\n\nSigned-off-by: David Woodhouse <David.Woodhouse@intel.com>\n[lizf: Backported to 3.4:\n - adjust context\n - drop the last part of the changes of the patch]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/428b68c783a12cc5517a49e549cd50c31d3b6d49"},{"sha":"b5c26f6d5ffd2cba99e00926156ff4a0af6b6174","author":{"name":"Daeho Jeong","email":"10047286f23c4492b9fcf1500c061890203906c4@samsung.com"},"message":"ext4, jbd2: ensure entering into panic after recording an error in superblock\n\ncommit 4327ba52afd03fc4b5afa0ee1d774c9c5b0e85c5 upstream.\n\nIf a EXT4 filesystem utilizes JBD2 journaling and an error occurs, the\njournaling will be aborted first and the error number will be recorded\ninto JBD2 superblock and, finally, the system will enter into the\npanic state in \"errors=panic\" option.  But, in the rare case, this\nsequence is little twisted like the below figure and it will happen\nthat the system enters into panic state, which means the system reset\nin mobile environment, before completion of recording an error in the\njournal superblock. In this case, e2fsck cannot recognize that the\nfilesystem failure occurred in the previous run and the corruption\nwouldn't be fixed.\n\nTask A                        Task B\next4_handle_error()\n-> jbd2_journal_abort()\n  -> __journal_abort_soft()\n    -> __jbd2_journal_abort_hard()\n    | -> journal->j_flags |= JBD2_ABORT;\n    |\n    |                         __ext4_abort()\n    |                         -> jbd2_journal_abort()\n    |                         | -> __journal_abort_soft()\n    |                         |   -> if (journal->j_flags & JBD2_ABORT)\n    |                         |           return;\n    |                         -> panic()\n    |\n    -> jbd2_journal_update_sb_errno()\n\nTested-by: Hobin Woo <hobin.woo@samsung.com>\nSigned-off-by: Daeho Jeong <daeho.jeong@samsung.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/b5c26f6d5ffd2cba99e00926156ff4a0af6b6174"},{"sha":"a083a39c8a050371924835bbc41147539b95dc82","author":{"name":"Larry Finger","email":"15b8df22a685ea626b641ec4b41ea74b2ea632fd@lwfinger.net"},"message":"staging: rtl8712: Add device ID for Sitecom WLA2100\n\ncommit 1e6e63283691a2a9048a35d9c6c59cf0abd342e4 upstream.\n\nThis adds the USB ID for the Sitecom WLA2100. The Windows 10 inf file\nwas checked to verify that the addition is correct.\n\nReported-by: Frans van de Wiel <fvdw@fvdw.eu>\nSigned-off-by: Larry Finger <Larry.Finger@lwfinger.net>\nCc: Frans van de Wiel <fvdw@fvdw.eu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/a083a39c8a050371924835bbc41147539b95dc82"},{"sha":"3a4e9749da6dbb3c73e75b2b357fd6046d7024a8","author":{"name":"Chen Yu","email":"ba33fa3ef7b3cb2220f0e8868cfc641388b29b1e@intel.com"},"message":"ACPI: Use correct IRQ when uninstalling ACPI interrupt handler\n\ncommit 49e4b84333f338d4f183f28f1f3c1131b9fb2b5a upstream.\n\nCurrently when the system is trying to uninstall the ACPI interrupt\nhandler, it uses acpi_gbl_FADT.sci_interrupt as the IRQ number.\nHowever, the IRQ number that the ACPI interrupt handled is installed\nfor comes from acpi_gsi_to_irq() and that is the number that should\nbe used for the handler removal.\n\nFix this problem by using the mapped IRQ returned from acpi_gsi_to_irq()\nas appropriate.\n\nAcked-by: Lv Zheng <lv.zheng@intel.com>\nSigned-off-by: Chen Yu <yu.c.chen@intel.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/3a4e9749da6dbb3c73e75b2b357fd6046d7024a8"},{"sha":"acdb6a4846507510404ab45cda30ecce71a84f8f","author":{"name":"Takashi Iwai","email":"dd0a9a4ae370c51e6d7099900a4bf6656524e055@suse.de"},"message":"ALSA: hda - Disable 64bit address for Creative HDA controllers\n\ncommit cadd16ea33a938d49aee99edd4758cc76048b399 upstream.\n\nWe've had many reports that some Creative sound cards with CA0132\ndon't work well.  Some reported that it starts working after reloading\nthe module, while some reported it starts working when a 32bit kernel\nis used.  All these facts seem implying that the chip fails to\ncommunicate when the buffer is located in 64bit address.\n\nThis patch addresses these issues by just adding AZX_DCAPS_NO_64BIT\nflag to the corresponding PCI entries.  I casually had a chance to\ntest an SB Recon3D board, and indeed this seems helping.\n\nAlthough this hasn't been tested on all Creative devices, it's safer\nto assume that this restriction applies to the rest of them, too.  So\nthe flag is applied to all Creative entries.\n\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\n[lizf: Backported to 3.4: drop the change to macro AZX_DCAPS_PRESET_CTHDA]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/acdb6a4846507510404ab45cda30ecce71a84f8f"},{"sha":"b057f7fe1f8c16fede18db0e3e865f0dc1dafff5","author":{"name":"sumit.saxena@avagotech.com","email":"5dcf75d1867621771bd752f052a02cf4b72fc0bf@avagotech.com"},"message":"megaraid_sas: Do not use PAGE_SIZE for max_sectors\n\ncommit 357ae967ad66e357f78b5cfb5ab6ca07fb4a7758 upstream.\n\nDo not use PAGE_SIZE marco to calculate max_sectors per I/O\nrequest. Driver code assumes PAGE_SIZE will be always 4096 which can\nlead to wrongly calculated value if PAGE_SIZE is not 4096. This issue\nwas reported in Ubuntu Bugzilla Bug #1475166.\n\nSigned-off-by: Sumit Saxena <sumit.saxena@avagotech.com>\nSigned-off-by: Kashyap Desai <kashyap.desai@avagotech.com>\nReviewed-by: Tomas Henzl <thenzl@redhat.com>\nReviewed-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/GalaticStryder/kernel_lge_msm8974/commits/b057f7fe1f8c16fede18db0e3e865f0dc1dafff5"}]}
{"actor":{"display_login":"GalaticStryder"}}