{"push_id":1421258622,"size":348,"distinct_size":348,"ref":"refs/heads/cm-14.1","head":"45b00226be2a154410d8cb4f491af78c29cbef9f","before":"e73421225958fc5bbff23dee870e65180c31797a","commits":[{"sha":"10ec32944eeb7398cc5f1162f71eb312b62258b6","author":{"name":"Tom Lendacky","email":"aae724d943dd57e8b9dec8b455e9688272d2d782@amd.com"},"message":"crypto: scatterwalk - Set the chain pointer indication bit\n\ncommit 41da8b5adba77e22584f8b45f9641504fa885308 upstream.\n\nThe scatterwalk_crypto_chain function invokes the scatterwalk_sg_chain\nfunction to chain two scatterlists, but the chain pointer indication\nbit is not set.  When the resulting scatterlist is used, for example,\nby sg_nents to count the number of scatterlist entries, a segfault occurs\nbecause sg_nents does not follow the chain pointer to the chained scatterlist.\n\nUpdate scatterwalk_sg_chain to set the chain pointer indication bit as is\ndone by the sg_chain function.\n\nSigned-off-by: Tom Lendacky <thomas.lendacky@amd.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/10ec32944eeb7398cc5f1162f71eb312b62258b6"},{"sha":"1982300f9983164caf561afbeff29a0bff2b991b","author":{"name":"Horia Geanta","email":"87fbee286af4b152b592859165e8b005642ca748@freescale.com"},"message":"crypto: ccm - Fix handling of zero plaintext when computing mac\n\ncommit 5638cabf3e4883f38dfb246c30980cebf694fbda upstream.\n\nThere are cases when cryptlen can be zero in crypto_ccm_auth():\n-encryptiom: input scatterlist length is zero (no plaintext)\n-decryption: input scatterlist contains only the mac\nplus the condition of having different source and destination buffers\n(or else scatterlist length = max(plaintext_len, ciphertext_len)).\n\nThese are not handled correctly, leading to crashes like:\n\nroot@p4080ds:~/crypto# insmod tcrypt.ko mode=45\n------------[ cut here ]------------\nkernel BUG at crypto/scatterwalk.c:37!\nOops: Exception in kernel mode, sig: 5 [#1]\nSMP NR_CPUS=8 P4080 DS\nModules linked in: tcrypt(+) crc32c xts xcbc vmac pcbc ecb gcm ghash_generic gf128mul ccm ctr seqiv\nCPU: 3 PID: 1082 Comm: cryptomgr_test Not tainted 3.11.0 #14\ntask: ee12c5b0 ti: eecd0000 task.ti: eecd0000\nNIP: c0204d98 LR: f9225848 CTR: c0204d80\nREGS: eecd1b70 TRAP: 0700   Not tainted  (3.11.0)\nMSR: 00029002 <CE,EE,ME>  CR: 22044022  XER: 20000000\n\nGPR00: f9225c94 eecd1c20 ee12c5b0 eecd1c28 ee879400 ee879400 00000000 ee607464\nGPR08: 00000001 00000001 00000000 006b0000 c0204d80 00000000 00000002 c0698e20\nGPR16: ee987000 ee895000 fffffff4 ee879500 00000100 eecd1d58 00000001 00000000\nGPR24: ee879400 00000020 00000000 00000000 ee5b2800 ee607430 00000004 ee607460\nNIP [c0204d98] scatterwalk_start+0x18/0x30\nLR [f9225848] get_data_to_compute+0x28/0x2f0 [ccm]\nCall Trace:\n[eecd1c20] [f9225974] get_data_to_compute+0x154/0x2f0 [ccm] (unreliable)\n[eecd1c70] [f9225c94] crypto_ccm_auth+0x184/0x1d0 [ccm]\n[eecd1cb0] [f9225d40] crypto_ccm_encrypt+0x60/0x2d0 [ccm]\n[eecd1cf0] [c020d77c] __test_aead+0x3ec/0xe20\n[eecd1e20] [c020f35c] test_aead+0x6c/0xe0\n[eecd1e40] [c020f420] alg_test_aead+0x50/0xd0\n[eecd1e60] [c020e5e4] alg_test+0x114/0x2e0\n[eecd1ee0] [c020bd1c] cryptomgr_test+0x4c/0x60\n[eecd1ef0] [c0047058] kthread+0xa8/0xb0\n[eecd1f40] [c000eb0c] ret_from_kernel_thread+0x5c/0x64\nInstruction dump:\n0f080000 81290024 552807fe 0f080000 5529003a 4bffffb4 90830000 39400000\n39000001 8124000c 2f890000 7d28579e <0f090000> 81240008 91230004 4e800020\n---[ end trace 6d652dfcd1be37bd ]---\n\nCc: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>\nSigned-off-by: Horia Geanta <horia.geanta@freescale.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/1982300f9983164caf561afbeff29a0bff2b991b"},{"sha":"3d9f4f60808b8d5f905ad071711510435c847c8a","author":{"name":"Tom Lendacky","email":"aae724d943dd57e8b9dec8b455e9688272d2d782@amd.com"},"message":"crypto: authenc - Find proper IV address in ablkcipher callback\n\ncommit fc019c7122dfcd69c50142b57a735539aec5da95 upstream.\n\nWhen performing an asynchronous ablkcipher operation the authenc\ncompletion callback routine is invoked, but it does not locate and use\nthe proper IV.\n\nThe callback routine, crypto_authenc_encrypt_done, is updated to use\nthe same method of calculating the address of the IV as is done in\ncrypto_authenc_encrypt function which sets up the callback.\n\nSigned-off-by: Tom Lendacky <thomas.lendacky@amd.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/3d9f4f60808b8d5f905ad071711510435c847c8a"},{"sha":"77e0161b5ff4ae53b599d55c3c30cad1faf1cc22","author":{"name":"Mark Brown","email":"bf2c7ef56f4d087c7cc4d81e9839c8674e3b6b2e@linaro.org"},"message":"ASoC: wm8990: Mark the register map as dirty when powering down\n\ncommit 2ab2b74277a86afe0dd92976db695a2bb8b93366 upstream.\n\nOtherwise we'll skip sync on resume.\n\nSigned-off-by: Mark Brown <broonie@linaro.org>\nAcked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/77e0161b5ff4ae53b599d55c3c30cad1faf1cc22"},{"sha":"a1375154020cf5266f98b7a2b2525466c0b1d5bc","author":{"name":"Bo Shen","email":"1430bdd0985e90231e9033f01f5b57eac51e4e6d@atmel.com"},"message":"ASoC: wm8731: fix dsp mode configuration\n\ncommit b4af6ef99a60c5b56df137d7accd81ba1ee1254e upstream.\n\nAccording to WM8731 \"PD, Rev 4.9 October 2012\" datasheet, when it\nworks in DSP mode A, LRP = 1, while works in DSP mode B, LRP = 0.\nSo, fix LRP for DSP mode as the datesheet specification.\n\nSigned-off-by: Bo Shen <voice.shen@atmel.com>\nAcked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>\nSigned-off-by: Mark Brown <broonie@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/a1375154020cf5266f98b7a2b2525466c0b1d5bc"},{"sha":"d28df0fe5a3c7cd3b9c4927b78d724e98e5177e3","author":{"name":"James Bottomley","email":"8881c6aa81429563aeea1d4ca0f7afad4cb4b3c4@Parallels.com"},"message":"SCSI: enclosure: fix WARN_ON in dual path device removing\n\ncommit a1470c7bf3a4676e62e4c0fb204e339399eb5c59 upstream.\n\nBug report from: wenxiong@linux.vnet.ibm.com\n\nThe issue is happened in dual controller configuration. We got the\nsysfs warnings when rmmod the ipr module.\n\nenclosure_unregister() in drivers/msic/enclosure.c, call device_unregister()\nfor each componment deivce, device_unregister() ->device_del()->kobject_del()\n->sysfs_remove_dir(). In sysfs_remove_dir(), set kobj->sd = NULL.\n\nFor each componment device,\nenclosure_component_release()->enclosure_remove_links()->sysfs_remove_link()\nin which checking kobj->sd again, it has been set as NULL when doing\ndevice_unregister. So we saw all these sysfs WARNING.\n\nTested-by: wenxiong@linux.vnet.ibm.com\nSigned-off-by: James Bottomley <JBottomley@Parallels.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/d28df0fe5a3c7cd3b9c4927b78d724e98e5177e3"},{"sha":"4fd8762fd8fa07217fc87f4f411f0689fa943f45","author":{"name":"Dan Williams","email":"11d4d1e92ac6a0e1ab4aaa72a56a5c1cae6b74af@intel.com"},"message":"SCSI: libsas: fix usage of ata_tf_to_fis\n\ncommit ae5fbae0ccd982dfca0ce363036ed92f5b13f150 upstream.\n\nSince commit 110dd8f19df5 \"[SCSI] libsas: fix scr_read/write users and\nupdate the libata documentation\" we have been passing pmp=1 and is_cmd=0\nto ata_tf_to_fis().  Praveen reports that eSATA attached drives do not\ndiscover correctly.  His investigation found that the BIOS was passing\npmp=0 while Linux was passing pmp=1 and failing to discover the drives.\nUpdate libsas to follow the libata example of pulling the pmp setting\nfrom the ata_link and correct is_cmd to be 1 since all tf's submitted\nthrough ->qc_issue are commands.  Presumably libsas lldds do not care\nabout is_cmd as they have sideband mechanisms to perform link\nmanagement.\n\nhttp://marc.info/?l=linux-scsi&m=138179681726990\n\n[jejb: checkpatch fix]\nSigned-off-by: Dan Williams <dan.j.williams@intel.com>\nReported-by: Praveen Murali <pmurali@logicube.com>\nTested-by: Praveen Murali <pmurali@logicube.com>\nSigned-off-by: James Bottomley <JBottomley@Parallels.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/4fd8762fd8fa07217fc87f4f411f0689fa943f45"},{"sha":"bcf0b0f789de0a4a983ed5bebae7189665f6ee6c","author":{"name":"Stephen M. Cameron","email":"fa47b794c86c730830ead6808a5b82991d882b51@beardog.cce.hp.com"},"message":"SCSI: hpsa: do not discard scsi status on aborted commands\n\ncommit 2e311fbabdc23b7eaec77313dc3b9a151a5407b5 upstream.\n\nWe inadvertantly discarded the scsi status for aborted commands.\nFor some commands (e.g. reads from tape drives) these can't be retried,\nand if we discarded the scsi status, the scsi mid layer couldn't notice\nanything was wrong and the error was not reported.\n\nSigned-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com>\nSigned-off-by: James Bottomley <JBottomley@Parallels.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/bcf0b0f789de0a4a983ed5bebae7189665f6ee6c"},{"sha":"99cc53fb6f82ad5a528dbb75076ed62ffbb1543d","author":{"name":"Stephen M. Cameron","email":"fa47b794c86c730830ead6808a5b82991d882b51@beardog.cce.hp.com"},"message":"SCSI: hpsa: return 0 from driver probe function on success, not 1\n\ncommit 88bf6d62db4393fa03a58bada9d746312d5b496f upstream.\n\nA return value of 1 is interpreted as an error.  See pci_driver.\nin local_pci_probe().  If you're wondering how this ever could\nhave worked, it's because it used to be the case that only return\nvalues less than zero were interpreted as failure.  But even in\nthe current kernel if the driver registers its various entry\npoints with the kernel, and then returns a value which is\ninterpreted as failure, those registrations aren't undone, so\nthe driver still mostly works.  However, the driver's remove\nfunction wouldn't be called on rmmod, and pci power management\nfunctions wouldn't work.  In the case of Smart Array, since it\nhas a battery backed cache (or else no cache) even if the driver\nis not shut down properly as long as there is no outstanding\ni/o, nothing too bad happens, which is why it took so long to\nnotice.\n\nRequesting backport to stable because the change to pci-driver.c\nwhich requires driver probe functions to return 0 occurred between\n2.6.35 and 2.6.36 (the pci power management breakage) and again\nbetween 3.7 and 3.8 (pci_dev->driver getting set to NULL in\nlocal_pci_probe() preventing driver remove function from being\ncalled on rmmod.)\n\nSigned-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com>\nSigned-off-by: James Bottomley <JBottomley@Parallels.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/99cc53fb6f82ad5a528dbb75076ed62ffbb1543d"},{"sha":"1560c3e777247f79ab8b77fab0e2a7ba95187186","author":{"name":"Linus Walleij","email":"b0d9e537b6c72323d8ac72352e58c452d7c4fc88@linaro.org"},"message":"net: smc91: fix crash regression on the versatile\n\ncommit a0c20fb02592d372e744d1d739cda3e1b3defaae upstream.\n\nAfter commit e9e4ea74f06635f2ffc1dffe5ef40c854faa0a90\n\"net: smc91x: dont't use SMC_outw for fixing up halfword-aligned data\"\nThe Versatile SMSC LAN91C111 is crashing like this:\n\n------------[ cut here ]------------\nkernel BUG at /home/linus/linux/drivers/net/ethernet/smsc/smc91x.c:599!\nInternal error: Oops - BUG: 0 [#1] ARM\nModules linked in:\nCPU: 0 PID: 43 Comm: udhcpc Not tainted 3.13.0-rc1+ #24\ntask: c6ccfaa0 ti: c6cd0000 task.ti: c6cd0000\nPC is at smc_hardware_send_pkt+0x198/0x22c\nLR is at smc_hardware_send_pkt+0x24/0x22c\npc : [<c01be324>]    lr : [<c01be1b0>]    psr: 20000013\nsp : c6cd1d08  ip : 00000001  fp : 00000000\nr10: c02adb08  r9 : 00000000  r8 : c6ced802\nr7 : c786fba0  r6 : 00000146  r5 : c8800000  r4 : c78d6000\nr3 : 0000000f  r2 : 00000146  r1 : 00000000  r0 : 00000031\nFlags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user\nControl: 0005317f  Table: 06cf4000  DAC: 00000015\nProcess udhcpc (pid: 43, stack limit = 0xc6cd01c0)\nStack: (0xc6cd1d08 to 0xc6cd2000)\n1d00:                   00000010 c8800000 c78d6000 c786fba0 c78d6000 c01be868\n1d20: c01be7a4 00004000 00000000 c786fba0 c6c12b80 c0208554 000004d0 c780fc60\n1d40: 00000220 c01fb734 00000000 00000000 00000000 c6c9a440 c6c12b80 c78d6000\n1d60: c786fba0 c6c9a440 00000000 c021d1d8 00000000 00000000 c6c12b80 c78d6000\n1d80: c786fba0 00000001 c6c9a440 c02087f8 c6c9a4a0 00080008 00000000 00000000\n1da0: c78d6000 c786fba0 c78d6000 00000138 00000000 00000000 00000000 00000000\n1dc0: 00000000 c027ba74 00000138 00000138 00000001 00000010 c6cedc00 00000000\n1de0: 00000008 c7404400 c6cd1eec c6cd1f14 c067a73c c065c0b8 00000000 c067a740\n1e00: 01ffffff 002040d0 00000000 00000000 00000000 00000000 00000000 ffffffff\n1e20: 43004400 00110022 c6cdef20 c027ae8c c6ccfaa0 be82d65c 00000014 be82d3cc\n1e40: 00000000 00000000 00000000 c01f2870 00000000 00000000 00000000 c6cd1e88\n1e60: c6ccfaa0 00000000 00000000 00000000 00000000 00000000 00000000 00000000\n1e80: 00000000 00000000 00000031 c7802310 c7802300 00000138 c7404400 c0771da0\n1ea0: 00000000 c6cd1eec c7800340 00000138 be82d65c 00000014 be82d3cc c6cd1f08\n1ec0: 00000014 00000000 c7404400 c7404400 00000138 c01f4628 c78d6000 00000000\n1ee0: 00000000 be82d3cc 00000138 c6cd1f08 00000014 c6cd1ee4 00000001 00000000\n1f00: 00000000 00000000 00080011 00000002 06000000 ffffffff 0000ffff 00000002\n1f20: 06000000 ffffffff 0000ffff c00928c8 c065c520 c6cd1f58 00000003 c009299c\n1f40: 00000003 c065c520 c7404400 00000000 c7404400 c01f2218 c78106b0 c7441cb0\n1f60: 00000000 00000006 c06799fc 00000000 00000000 00000006 00000000 c01f3ee0\n1f80: 00000000 00000000 be82d678 be82d65c 00000014 00000001 00000122 c00139c8\n1fa0: c6cd0000 c0013840 be82d65c 00000014 00000006 be82d3cc 00000138 00000000\n1fc0: be82d65c 00000014 00000001 00000122 00000000 00000000 00018cb1 00000000\n1fe0: 00003801 be82d3a8 0003a0c7 b6e9af08 60000010 00000006 00000000 00000000\n[<c01be324>] (smc_hardware_send_pkt+0x198/0x22c) from [<c01be868>] (smc_hard_start_xmit+0xc4/0x1e8)\n[<c01be868>] (smc_hard_start_xmit+0xc4/0x1e8) from [<c0208554>] (dev_hard_start_xmit+0x460/0x4cc)\n[<c0208554>] (dev_hard_start_xmit+0x460/0x4cc) from [<c021d1d8>] (sch_direct_xmit+0x94/0x18c)\n[<c021d1d8>] (sch_direct_xmit+0x94/0x18c) from [<c02087f8>] (dev_queue_xmit+0x238/0x42c)\n[<c02087f8>] (dev_queue_xmit+0x238/0x42c) from [<c027ba74>] (packet_sendmsg+0xbe8/0xd28)\n[<c027ba74>] (packet_sendmsg+0xbe8/0xd28) from [<c01f2870>] (sock_sendmsg+0x84/0xa8)\n[<c01f2870>] (sock_sendmsg+0x84/0xa8) from [<c01f4628>] (SyS_sendto+0xb8/0xdc)\n[<c01f4628>] (SyS_sendto+0xb8/0xdc) from [<c0013840>] (ret_fast_syscall+0x0/0x2c)\nCode: e3130002 1a000001 e3130001 0affffcd (e7f001f2)\n---[ end trace 81104fe70e8da7fe ]---\nKernel panic - not syncing: Fatal exception in interrupt\n\nThis is because the macro operations in smc91x.h defined\nfor Versatile are missing SMC_outsw() as used in this\ncommit.\n\nThe Versatile needs and uses the same accessors as the other\nplatforms in the first if(...) clause, just switch it to using\nthat and we have one problem less to worry about.\n\nThis includes a hunk of a patch from Will Deacon fixin\nthe other 32bit platforms as well: Innokom, Ramses, PXA,\nPCM027.\n\nCheckpatch complains about spacing, but I have opted to\nfollow the style of this .h-file.\n\nCc: Russell King <linux@arm.linux.org.uk>\nCc: Nicolas Pitre <nico@fluxnic.net>\nCc: Eric Miao <eric.y.miao@gmail.com>\nCc: Jonathan Cameron <jic23@cam.ac.uk>\nSigned-off-by: Will Deacon <will.deacon@arm.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nConflicts:\n\tdrivers/net/ethernet/smsc/smc91x.h","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/1560c3e777247f79ab8b77fab0e2a7ba95187186"},{"sha":"555e3dfafb010c3882dc2161d55cf354057dcebc","author":{"name":"Trond Myklebust","email":"3afdbc35768b1a8213e66ad125a6f3dde75e61dd@netapp.com"},"message":"NFSv4: Update list of irrecoverable errors on DELEGRETURN\n\ncommit c97cf606e43b85a6cf158b810375dd77312024db upstream.\n\nIf the DELEGRETURN errors out with something like NFS4ERR_BAD_STATEID\nthen there is no recovery possible. Just quit without returning an error.\n\nAlso, note that the client must not assume that the NFSv4 lease has been\nrenewed when it sees an error on DELEGRETURN.\n\nSigned-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/555e3dfafb010c3882dc2161d55cf354057dcebc"},{"sha":"28f2d98e5f8235ab4809c2e81b297980a1b38bde","author":{"name":"Liu Gang","email":"80ad1551db20d20a941021e5ec2f529607aea500@freescale.com"},"message":"powerpc/gpio: Fix the wrong GPIO input data on MPC8572/MPC8536\n\ncommit 1aeef303b5d9e243c41d5b80f8bb059366514a10 upstream.\n\nFor MPC8572/MPC8536, the status of GPIOs defined as output\ncannot be determined by reading GPDAT register, so the code\nuse shadow data register instead. But the code may give the\nwrong status of GPIOs defined as input under some scenarios:\n\n1. If some pins were configured as inputs and were asserted\nhigh before booting the kernel, the shadow data has been\ninitialized with those pin values.\n2. Some pins have been configured as output first and have\nbeen set to the high value, then reconfigured as input.\n\nThe above cases will make the shadow data for those input\npins to be set to high. Then reading the pin status will\nalways return high even if the actual pin status is low.\n\nThe code should eliminate the effects of the shadow data to\nthe input pins, and the status of those pins should be\nread directly from GPDAT.\n\nAcked-by: Scott Wood <scottwood@freescale.com>\nAcked-by: Anatolij Gustschin <agust@denx.de>\nSigned-off-by: Liu Gang <Gang.Liu@freescale.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/28f2d98e5f8235ab4809c2e81b297980a1b38bde"},{"sha":"668f5f654d8f811d4ed781c1483d94151a79c0a7","author":{"name":"Laxman Dewangan","email":"5f7cfded8d08b39ace2784facb5a59c87054b040@nvidia.com"},"message":"irq: Enable all irqs unconditionally in irq_resume\n\ncommit ac01810c9d2814238f08a227062e66a35a0e1ea2 upstream.\n\nWhen the system enters suspend, it disables all interrupts in\nsuspend_device_irqs(), including the interrupts marked EARLY_RESUME.\n\nOn the resume side things are different. The EARLY_RESUME interrupts\nare reenabled in sys_core_ops->resume and the non EARLY_RESUME\ninterrupts are reenabled in the normal system resume path.\n\nWhen suspend_noirq() failed or suspend is aborted for any other\nreason, we might omit the resume side call to sys_core_ops->resume()\nand therefor the interrupts marked EARLY_RESUME are not reenabled and\nstay disabled forever.\n\nTo solve this, enable all irqs unconditionally in irq_resume()\nregardless whether interrupts marked EARLY_RESUMEhave been already\nenabled or not.\n\nThis might try to reenable already enabled interrupts in the non\nfailure case, but the only affected platform is XEN and it has been\nconfirmed that it does not cause any side effects.\n\n[ tglx: Massaged changelog. ]\n\nSigned-off-by: Laxman Dewangan <ldewangan@nvidia.com>\nAcked-by-and-tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nAcked-by: Heiko Stuebner <heiko@sntech.de>\nReviewed-by: Pavel Machek <pavel@ucw.cz>\nCc: <ian.campbell@citrix.com>\nCc: <rjw@rjwysocki.net>\nCc: <len.brown@intel.com>\nCc: <gregkh@linuxfoundation.org>\nLink: http://lkml.kernel.org/r/1385388587-16442-1-git-send-email-ldewangan@nvidia.com\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/668f5f654d8f811d4ed781c1483d94151a79c0a7"},{"sha":"107d376ca98ec89265c93d71d93cd0b1eba07b5e","author":{"name":"Shawn Landden","email":"1ba305e3abcdbdd4a853e81615dfcbc6c9692d58@churchofgit.com"},"message":"net: update consumers of MSG_MORE to recognize MSG_SENDPAGE_NOTLAST\n\ncommit d3f7d56a7a4671d395e8af87071068a195257bf6 upstream.\n\nCommit 35f9c09fe (tcp: tcp_sendpages() should call tcp_push() once)\nadded an internal flag MSG_SENDPAGE_NOTLAST, similar to\nMSG_MORE.\n\nalgif_hash, algif_skcipher, and udp used MSG_MORE from tcp_sendpages()\nand need to see the new flag as identical to MSG_MORE.\n\nThis fixes sendfile() on AF_ALG.\n\nv3: also fix udp\n\nCc: Tom Herbert <therbert@google.com>\nCc: Eric Dumazet <eric.dumazet@gmail.com>\nCc: David S. Miller <davem@davemloft.net>\nReported-and-tested-by: Shawn Landden <shawnlandden@gmail.com>\nOriginal-patch: Richard Weinberger <richard@nod.at>\nSigned-off-by: Shawn Landden <shawn@churchofgit.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/107d376ca98ec89265c93d71d93cd0b1eba07b5e"},{"sha":"4e476a084a0f7fb8cf8740fb3d9d0bbec5cd5b42","author":{"name":"Tom Gundersen","email":"cc4f35c29a4fef602c94287b93bac5a51ca773ee@jklm.no"},"message":"Input: allow deselecting serio drivers even without CONFIG_EXPERT\n\ncommit bcd2623073e98f69f84720308db0b142c4da0bd6 upstream.\n\nThere is plenty of consumer hardware (e.g., mac books) that does not use AT\nkeyboards or PS/2 mice. It therefore makes sense for distro kernels to\nbuild the related drivers as modules to avoid loading them on hardware that\ndoes not need them. As such, these options should no longer be protected by\nEXPERT.\n\nMoreover, building these drivers as modules gets rid of the following ugly\nerror during boot:\n\n[    2.337745] i8042: PNP: No PS/2 controller found. Probing ports directly.\n[    3.439537] i8042: No controller found\n\nSigned-off-by: Tom Gundersen <teg@jklm.no>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/4e476a084a0f7fb8cf8740fb3d9d0bbec5cd5b42"},{"sha":"f86a7c12b2c2be319e3172e744b71b7787f049bf","author":{"name":"Tom Gundersen","email":"cc4f35c29a4fef602c94287b93bac5a51ca773ee@jklm.no"},"message":"Input: mousedev - allow disabling even without CONFIG_EXPERT\n\ncommit dfaaed08ecc01bd513248ba7999daf50ce028352 upstream.\n\nMoust (if not all) modern software, including X, uses /dev/eventX rather than\nthe legacy /dev/mouseX devices. It therefore makes sense for general-purpose\n(distro) kernels to use MOUSEDV=m (or even n), so let's drop the EXPERT=y\nrequirement.\n\nSigned-off-by: Tom Gundersen <teg@jklm.no>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/f86a7c12b2c2be319e3172e744b71b7787f049bf"},{"sha":"3e7d280d621e8c009338023cba54c739bca55fe4","author":{"name":"Sergei Trofimovich","email":"1326cbd996edcc149ddc3d9108286d7438e81856@gentoo.org"},"message":"um: add missing declaration of 'getrlimit()' and friends\n\ncommit fdfa4c952844fce881df8c76de9c7180cbe913ab upstream.\n\narch/um/os-Linux/start_up.c: In function 'check_coredump_limit':\narch/um/os-Linux/start_up.c:338:16: error: storage size of 'lim' isn't known\narch/um/os-Linux/start_up.c:339:2: error: implicit declaration of function 'getrlimit' [-Werror=implicit-function-declaration]\n\nSigned-off-by: Sergei Trofimovich <slyfox@gentoo.org>\nCC: Jeff Dike <jdike@addtoit.com>\nCC: Richard Weinberger <richard@nod.at>\nCC: Al Viro <viro@zeniv.linux.org.uk>\nCC: user-mode-linux-devel@lists.sourceforge.net\nCC: user-mode-linux-user@lists.sourceforge.net\nCC: linux-kernel@vger.kernel.org\nSigned-off-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/3e7d280d621e8c009338023cba54c739bca55fe4"},{"sha":"2727de5b4bf589c4a122730c802b583fcebdee91","author":{"name":"James Ralston","email":"47f1ef8b24df3abe2af998ed09b97db700ba9dcd@intel.com"},"message":"ahci: Add Device IDs for Intel Lynx Point-LP PCH\n\ncommit 77b12bc9cf7b10c7c1a04ca45272fbb4287902d0 upstream.\n\nThis patch adds the AHCI-mode SATA Device IDs for the Intel Lynx Point-LP PCH\n\nSigned-off-by: James Ralston <james.d.ralston@intel.com>\nSigned-off-by: Jeff Garzik <jgarzik@redhat.com>\nCc: Ong Boon Leong <boon.leong.ong@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/2727de5b4bf589c4a122730c802b583fcebdee91"},{"sha":"9657eb7a78adc959fbf60af58e63f7e17cf91c37","author":{"name":"Seth Heasley","email":"bd420b9e37749e9fa2745965fe57e09433240728@intel.com"},"message":"ahci: AHCI-mode SATA patch for Intel Avoton DeviceIDs\n\ncommit 29e674dd5c8e781589f09c3ee139c80f6da274e4 upstream.\n\nThis patch adds the AHCI and RAID-mode SATA DeviceIDs for the Intel Avoton SOC.\n\nSigned-off-by: Seth Heasley <seth.heasley@intel.com>\nSigned-off-by: Jeff Garzik <jgarzik@redhat.com>\nCc: Ong Boon Leong <boon.leong.ong@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/9657eb7a78adc959fbf60af58e63f7e17cf91c37"},{"sha":"519ea3406d59527f29fe48f08d6294b637408a94","author":{"name":"Seth Heasley","email":"bd420b9e37749e9fa2745965fe57e09433240728@intel.com"},"message":"i2c: i801: SMBus patch for Intel Avoton DeviceIDs\n\ncommit c2db409cbc8751ccc7e6d2cc2e41af0d12ea637f upstream.\n\nThis patch adds the PCU SMBus DeviceID for the Intel Avoton SOC.\n\nSigned-off-by: Seth Heasley <seth.heasley@intel.com>\nReviewed-by: Jean Delvare <khali@linux-fr.org>\nSigned-off-by: Wolfram Sang <w.sang@pengutronix.de>\nCc: \"Ong, Boon Leong\" <boon.leong.ong@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_samsung_klte/commits/519ea3406d59527f29fe48f08d6294b637408a94"}]}
{"actor":{"display_login":"cm-gerrit"}}