{"push_id":1286913307,"size":90,"distinct_size":90,"ref":"refs/heads/android-msm-hammerhead-3.4-marshmallow-mr2","head":"52a5d2f0122a18ae1344461fccf284a8240b3ab6","before":"6a99a02ceb043ec80266046620273e2cbaf3aa95","commits":[{"sha":"fbd3360af54c417bcc032b38cce47a49475f57bb","author":{"name":"Tilman Schmidt","email":"44933cffbd4fa0f6a7883913f81d3918a4b79830@imap.cc"},"message":"isdn/gigaset: ratelimit CAPI message dumps\n\ncommit 8e618aad5348b6e6c5a90e8d97ea643197963b20 upstream.\n\nIntroduce a global ratelimit for CAPI message dumps to protect\nagainst possible log flood.\nDrop the ratelimit for ignored messages which is now covered by the\nglobal one.\n\nSigned-off-by: Tilman Schmidt <tilman@imap.cc>\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/anthyava/android_kernel_lge_hammerhead/commits/fbd3360af54c417bcc032b38cce47a49475f57bb"},{"sha":"9265e43adde9396eed736b3b14ad78f83b929973","author":{"name":"Tilman Schmidt","email":"44933cffbd4fa0f6a7883913f81d3918a4b79830@imap.cc"},"message":"isdn/gigaset: fix CAPI disconnect B3 handling\n\ncommit 62a1cfe052346b96a552b6a9178d412c709711bb upstream.\n\nIf DISCONNECT_B3_IND was synthesized because of a DISCONNECT_REQ\nwith existing logical connections, the connection state wasn't\nupdated accordingly. Also the emitted DISCONNECT_B3_IND message\nwasn't included in the debug log as requested.\nThis patch fixes both of these issues.\n\nSigned-off-by: Tilman Schmidt <tilman@imap.cc>\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/anthyava/android_kernel_lge_hammerhead/commits/9265e43adde9396eed736b3b14ad78f83b929973"},{"sha":"68efeab157f2bfbb1e9c1c30b53f74a1bb8eb4b0","author":{"name":"Tilman Schmidt","email":"44933cffbd4fa0f6a7883913f81d3918a4b79830@imap.cc"},"message":"isdn/gigaset: improve error handling querying firmware version\n\ncommit e055d03dc088a990fe5ea24a2d64033a168da23c upstream.\n\nAn out-of-place \"OK\" response to the \"AT+GMR\" (get firmware version)\ncommand turns out to be, more often than not, a delayed response to\na previous command rather than an actual error, so continue waiting\nfor the version number in that case.\n\nSigned-off-by: Tilman Schmidt <tilman@imap.cc>\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/anthyava/android_kernel_lge_hammerhead/commits/68efeab157f2bfbb1e9c1c30b53f74a1bb8eb4b0"},{"sha":"4e054f624cb7dfa4189aa183f37bdefa52882f55","author":{"name":"Linus Torvalds","email":"ead7104581934751970e9decb2db5deb20a9e407@linux-foundation.org"},"message":"vfs: make AIO use the proper rw_verify_area() area helpers\n\ncommit a70b52ec1aaeaf60f4739edb1b422827cb6f3893 upstream.\n\nWe had for some reason overlooked the AIO interface, and it didn't use\nthe proper rw_verify_area() helper function that checks (for example)\nmandatory locking on the file, and that the size of the access doesn't\ncause us to overflow the provided offset limits etc.\n\nInstead, AIO did just the security_file_permission() thing (that\nrw_verify_area() also does) directly.\n\nThis fixes it to do all the proper helper functions, which not only\nmeans that now mandatory file locking works with AIO too, we can\nactually remove lines of code.\n\nReported-by: Manish Honap <manish_honap_vit@yahoo.co.in>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/4e054f624cb7dfa4189aa183f37bdefa52882f55"},{"sha":"cb220ef8f1f099b8755ba7a7d7aecfd0db533e10","author":{"name":"Luis R. Rodriguez","email":"8f3d65a34b2ac5519a4848313a4f439b5d5e0fef@frijolero.org"},"message":"cfg80211: warn if db.txt is empty with CONFIG_CFG80211_INTERNAL_REGDB\n\ncommit 80007efeff0568375b08faf93c7aad65602cb97e upstream.\n\nIt has happened twice now where elaborate troubleshooting has\nundergone on systems where CONFIG_CFG80211_INTERNAL_REGDB [0]\nhas been set but yet net/wireless/db.txt was not updated.\n\nDespite the documentation on this it seems system integrators could\nuse some more help with this, so throw out a kernel warning at boot time\nwhen their database is empty.\n\nThis does mean that the error-prone system integrator won't likely\nrealize the issue until they boot the machine but -- it does not seem\nto make sense to enable a build bug breaking random build testing.\n\n[0] http://wireless.kernel.org/en/developers/Regulatory/CRDA#CONFIG_CFG80211_INTERNAL_REGDB\n\nCc: Stephen Rothwell <sfr@canb.auug.org.au>\nCc: Youngsin Lee <youngsin@qualcomm.com>\nCc: Raja Mani <rmani@qca.qualcomm.com>\nCc: Senthil Kumar Balasubramanian <senthilb@qca.qualcomm.com>\nCc: Vipin Mehta <vipimeht@qca.qualcomm.com>\nCc: yahuan@qca.qualcomm.com\nCc: jjan@qca.qualcomm.com\nCc: vthiagar@qca.qualcomm.com\nCc: henrykim@qualcomm.com\nCc: jouni@qca.qualcomm.com\nCc: athiruve@qca.qualcomm.com\nCc: cjkim@qualcomm.com\nCc: philipk@qca.qualcomm.com\nCc: sunnykim@qualcomm.com\nCc: sskwak@qualcomm.com\nCc: kkim@qualcomm.com\nCc: mattbyun@qualcomm.com\nCc: ryanlee@qualcomm.com\nCc: simbap@qualcomm.com\nCc: krislee@qualcomm.com\nCc: conner@qualcomm.com\nCc: hojinkim@qualcomm.com\nCc: honglee@qualcomm.com\nCc: johnwkim@qualcomm.com\nCc: jinyong@qca.qualcomm.com\nSigned-off-by: Luis R. Rodriguez <mcgrof@frijolero.org>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/cb220ef8f1f099b8755ba7a7d7aecfd0db533e10"},{"sha":"2e7c41bae22e7d9fc5448d97426d8214247c1465","author":{"name":"Mark Brown","email":"bf2c7ef56f4d087c7cc4d81e9839c8674e3b6b2e@opensource.wolfsonmicro.com"},"message":"regulator: core: Release regulator-regulator supplies on error\n\ncommit e81dba85c6388dfabcb76cbc2b8bd02836a53ae5 upstream.\n\nIf we fail while registering a regulator make sure we release the supply\nfor the regulator if there is one.\n\nSigned-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>\nAcked-by: Liam Girdwood <lrg@ti.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/2e7c41bae22e7d9fc5448d97426d8214247c1465"},{"sha":"bdb9a9fa5e6988ca0d41f913d53af08369a6b206","author":{"name":"Linus Torvalds","email":"ead7104581934751970e9decb2db5deb20a9e407@linux-foundation.org"},"message":"Fix blocking allocations called very early during bootup\n\ncommit 31a67102f4762df5544bc2dfb34a931233d2a5b2 upstream.\n\nDuring early boot, when the scheduler hasn't really been fully set up,\nwe really can't do blocking allocations because with certain (dubious)\nconfigurations the \"might_resched()\" calls can actually result in\nscheduling events.\n\nWe could just make such users always use GFP_ATOMIC, but quite often the\ncode that does the allocation isn't really aware of the fact that the\nscheduler isn't up yet, and forcing that kind of random knowledge on the\ninitialization code is just annoying and not good for anybody.\n\nAnd we actually have a the 'gfp_allowed_mask' exactly for this reason:\nit's just that the kernel init sequence happens to set it to allow\nblocking allocations much too early.\n\nSo move the 'gfp_allowed_mask' initialization from 'start_kernel()'\n(which is some of the earliest init code, and runs with preemption\ndisabled for good reasons) into 'kernel_init()'.  kernel_init() is run\nin the newly created thread that will become the 'init' process, as\nopposed to the early startup code that runs within the context of what\nwill be the first idle thread.\n\nSo by the time we reach 'kernel_init()', we know that the scheduler must\nbe at least limping along, because we've already scheduled from the idle\nthread into the init thread.\n\nReported-by: Steven Rostedt <rostedt@goodmis.org>\nCc: David Rientjes <rientjes@google.com>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/bdb9a9fa5e6988ca0d41f913d53af08369a6b206"},{"sha":"23cefb5e5091422bc5980c46a264183a5173d33b","author":{"name":"Heiko Carstens","email":"b2244c494cfb2f2e9003288a5a0aae79bf12423b@de.ibm.com"},"message":"s390/pfault: fix task state race\n\ncommit d5e50a51ccbda36b379aba9d1131a852eb908dda upstream.\n\nWhen setting the current task state to TASK_UNINTERRUPTIBLE this can\nrace with a different cpu. The other cpu could set the task state after\nit inspected it (while it was still TASK_RUNNING) to TASK_RUNNING which\nwould change the state from TASK_UNINTERRUPTIBLE to TASK_RUNNING again.\n\nThis race was always present in the pfault interrupt code but didn't\ncause anything harmful before commit f2db2e6c \"[S390] pfault: cpu hotplug\nvs missing completion interrupts\" which relied on the fact that after\nsetting the task state to TASK_UNINTERRUPTIBLE the task would really\nsleep.\nSince this is not necessarily the case the result may be a list corruption\nof the pfault_list or, as observed, a use-after-free bug while trying to\naccess the task_struct of a task which terminated itself already.\n\nTo fix this, we need to get a reference of the affected task when receiving\nthe initial pfault interrupt and add special handling if we receive yet\nanother initial pfault interrupt when the task is already enqueued in the\npfault list.\n\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nReviewed-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/23cefb5e5091422bc5980c46a264183a5173d33b"},{"sha":"d9608586dc81054daf8852f942a20b552c041f29","author":{"name":"nagalakshmi.nandigama@lsi.com","email":"18b84d46030990b4d6da816576b13d03286ee23e@lsi.com"},"message":"SCSI: mpt2sas: Fix for panic happening because of improper memory allocation\n\ncommit e42fafc25fa86c61824e8d4c5e7582316415d24f upstream.\n\nThe ioc->pfacts member in the IOC structure is getting set to zero\nfollowing a call to _base_get_ioc_facts due to the memset in that routine.\nSo if the ioc->pfacts was read after a host reset, there would be a NULL\npointer dereference. The routine _base_get_ioc_facts is called from context\nof host reset.  The problem in _base_get_ioc_facts  is the size of\nMpi2IOCFactsReply is 64, whereas the sizeof \"struct mpt2sas_facts\" is 60,\nso there is a four byte overflow resulting from the memset.\n\nAlso, there is memset in _base_get_port_facts using the incorrect structure,\nit should be \"struct mpt2sas_port_facts\" instead of Mpi2PortFactsReply.\n\nSigned-off-by: Nagalakshmi Nandigama <nagalakshmi.nandigama@lsi.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/anthyava/android_kernel_lge_hammerhead/commits/d9608586dc81054daf8852f942a20b552c041f29"},{"sha":"4f80184000c7a0e4ae68160885668b34e91d0c4a","author":{"name":"Dan Williams","email":"11d4d1e92ac6a0e1ab4aaa72a56a5c1cae6b74af@intel.com"},"message":"isci: fix oem parameter validation on single controller skus\n\ncommit fc25f79af321c01a739150ba2c09435cf977a63d upstream.\n\nOEM parameters [1] are parsed from the platform option-rom / efi\ndriver.  By default the driver was validating the parameters for the\ndual-controller case, but in single-controller case only the first set\nof parameters may be valid.\n\nLimit the validation to the number of actual controllers detected\notherwise the driver may fail to parse the valid parameters leading to\ndriver-load or runtime failures.\n\n[1] the platform specific set of phy address, configuration,and analog\n    tuning values\n\nReported-by: Dave Jiang <dave.jiang@intel.com>\nTested-by: Dave Jiang <dave.jiang@intel.com>\nSigned-off-by: Dan Williams <dan.j.williams@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/4f80184000c7a0e4ae68160885668b34e91d0c4a"},{"sha":"80b85c7f0dc4ee819e2c51bb79e12c6ff22f5168","author":{"name":"Steve Wise","email":"767c8fb6a78e68a8cc442ab232ab8748ae8710a2@opengridcomputing.com"},"message":"RDMA/cxgb4: Always wake up waiters in c4iw_peer_abort_intr()\n\ncommit 0f1dcfae6bc5563424346ad3a03282b8235a4c33 upstream.\n\nThis fixes a race where an ingress abort fails to wake up the thread\nblocked in rdma_init() causing the app to hang.\n\nSigned-off-by: Steve Wise <swise@opengridcomputing.com>\nSigned-off-by: Roland Dreier <roland@purestorage.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/80b85c7f0dc4ee819e2c51bb79e12c6ff22f5168"},{"sha":"83c7c3e1154ae40b2cf3938347534530eef05616","author":{"name":"Steve Wise","email":"767c8fb6a78e68a8cc442ab232ab8748ae8710a2@opengridcomputing.com"},"message":"RDMA/cxgb4: Use dst parameter in import_ep()\n\ncommit bd61baaf59669accae2720799394a51fecabe5d9 upstream.\n\nFunction import_ep() is incorrectly using ep->dst instead of the dst\nptr passed in.  This causes a crash when accepting new rdma connections\nbecase ep->dst is not initialized yet.\n\nSigned-off-by: Steve Wise <swise@opengridcomputing.com>\nSigned-off-by: Roland Dreier <roland@purestorage.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/83c7c3e1154ae40b2cf3938347534530eef05616"},{"sha":"955f6c09ef98dde15ab9adfa6441239ae31ba9b0","author":{"name":"Steve Wise","email":"767c8fb6a78e68a8cc442ab232ab8748ae8710a2@opengridcomputing.com"},"message":"RDMA/cxgb4: Drop peer_abort when no endpoint found\n\ncommit 14b9222808bb8bfefc71f72bc0dbdcf3b2f0140f upstream.\n\nLog a warning and drop the abort message.  Otherwise we will do a\nbogus wake_up() and crash.\n\nSigned-off-by: Steve Wise <swise@opengridcomputing.com>\nSigned-off-by: Roland Dreier <roland@purestorage.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/955f6c09ef98dde15ab9adfa6441239ae31ba9b0"},{"sha":"f0c07ab5aeb71b2a89b9930f198ef24a5ffc3f46","author":{"name":"Thomas Gleixner","email":"352b5f5ba0189d2583768a9bb8247f98115b9038@linutronix.de"},"message":"powerpc: Fix broken cpu_idle_wait() implementation\n\ncommit 9cd75e13de2dcf32ecc21c7f277cff3c0ced059e upstream.\n\ncommit 771dae818 (powerpc/cpuidle: Add cpu_idle_wait() to allow\nswitching of idle routines) implemented cpu_idle_wait() for powerpc.\n\nThe changelog says:\n \"The equivalent routine for x86 is in arch/x86/kernel/process.c\n  but the powerpc implementation is different.\":\n\nUnfortunately the changelog is completely useless as it does not tell\n_WHY_ it is different.\n\nAside of being different the implementation is patently wrong.\n\nThe rescheduling IPI is async. That means that there is no guarantee,\nthat the other cores have executed the IPI when cpu_idle_wait()\nreturns. But that's the whole purpose of this function: to guarantee\nthat no CPU uses the old idle handler anymore.\n\nUse the smp_functional_call() based implementation, which fulfils the\nrequirements.\n\n[ This code is going to replaced by a core version to remove all the\n  pointless copies in arch/*, but this one should go to stable ]\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nAcked-by: Peter Zijlstra <peterz@infradead.org>\nCc: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>\nCc: Trinabh Gupta <g.trinabh@gmail.com>\nCc: Arun R Bharadwaj <arun.r.bharadwaj@gmail.com>\nAcked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nLink: http://lkml.kernel.org/r/20120507175651.980164748@linutronix.de\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/f0c07ab5aeb71b2a89b9930f198ef24a5ffc3f46"},{"sha":"ae5903cdd733c2374d60d104f06dc8a226341685","author":{"name":"David Howells","email":"358fdf7bce8223edb2a0d846104bf62a286894d5@redhat.com"},"message":"KEYS: Use the compat keyctl() syscall wrapper on Sparc64 for Sparc32 compat\n\ncommit 45de6767dc51358a188f75dc4ad9dfddb7fb9480 upstream.\n\nUse the 32-bit compat keyctl() syscall wrapper on Sparc64 for Sparc32 binary\ncompatibility.\n\nWithout this, keyctl(KEYCTL_INSTANTIATE_IOV) is liable to malfunction as it\nuses an iovec array read from userspace - though the kernel should survive this\nas it checks pointers and sizes anyway.\n\nI think all the other keyctl() function should just work, provided (a) the top\n32-bits of each 64-bit argument register are cleared prior to invoking the\nsyscall routine, and the 32-bit address space is right at the 0-end of the\n64-bit address space.  Most of the arguments are 32-bit anyway, and so for\nthose clearing is not required.\n\nSigned-off-by: David Howells <dhowells@redhat.com\ncc: \"David S. Miller\" <davem@davemloft.net>\ncc: sparclinux@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/ae5903cdd733c2374d60d104f06dc8a226341685"},{"sha":"07ea29e3c76b7ecb8d7dce36ac6bdea124622d32","author":{"name":"Eric Paris","email":"990fee34756ded6b820fae429c8a566a036fd47d@redhat.com"},"message":"SELinux: if sel_make_bools errors don't leave inconsistent state\n\ncommit 154c50ca4eb9ae472f50b6a481213e21ead4457d upstream.\n\nWe reset the bool names and values array to NULL, but do not reset the\nnumber of entries in these arrays to 0.  If we error out and then get back\ninto this function we will walk these NULL pointers based on the belief\nthat they are non-zero length.\n\nSigned-off-by: Eric Paris <eparis@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/07ea29e3c76b7ecb8d7dce36ac6bdea124622d32"},{"sha":"9636e466320735be3a69af8e93659da0957c1d13","author":{"name":"Laurent Pinchart","email":"8b14580067f63df365ab75f40300acb6346a24eb@ideasonboard.com"},"message":"fbdev: sh_mobile_lcdc: Don't confuse line size with pitch\n\ncommit 72c04af9a2d57b7945cf3de8e71461bd80695d50 upstream.\n\nWhen using the MERAM the LCDC line size needs to be programmed with a\nMERAM-specific value different than the real frame buffer pitch. Fix it.\n\nReported-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>\nSigned-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nAcked-by: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/9636e466320735be3a69af8e93659da0957c1d13"},{"sha":"603b239169b4ff5baad134bf39fca5773962fd47","author":{"name":"Yishai Hadas","email":"cdd9576b4bc26a50abc68023908fbd641dc82652@mellanox.com"},"message":"IB/core: Fix mismatch between locked and pinned pages\n\ncommit c4870eb874ac16dccef40e1bc7a002c7e9156adc upstream.\n\nCommit bc3e53f682d9 (\"mm: distinguish between mlocked and pinned\npages\") introduced a separate counter for pinned pages and used it in\nthe IB stack.  However, in ib_umem_get() the pinned counter is\nincremented, but ib_umem_release() wrongly decrements the locked\ncounter.  Fix this.\n\nSigned-off-by: Yishai Hadas <yishaih@mellanox.com>\nReviewed-by: Christoph Lameter <cl@linux.com>\nSigned-off-by: Roland Dreier <roland@purestorage.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/603b239169b4ff5baad134bf39fca5773962fd47"},{"sha":"0c5eaec9f4c09c2f28f10100f586e869644b4042","author":{"name":"Julia Lawall","email":"5f26763d26f96d414e30b3f33734591afe022543@lip6.fr"},"message":"drivers/staging/comedi/comedi_fops.c: add missing vfree\n\ncommit abae41e6438b798e046d721b6ccdd55b4a398170 upstream.\n\naux_free is freed on all other exits from the function.  By removing the\nreturn, we can benefit from the vfree already at the end of the function.\n\nSigned-off-by: Julia Lawall <Julia.Lawall@lip6.fr>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/0c5eaec9f4c09c2f28f10100f586e869644b4042"},{"sha":"e40ce13c61ab258f65a20c8332c85e648b641046","author":{"name":"Robert Richter","email":"8d069a45895966ff08afa5f2812d9cbcfb14c986@amd.com"},"message":"perf/x86: Update event scheduling constraints for AMD family 15h models\n\ncommit 5bcdf5e4fee3c45e1281c25e4941f2163cb28c65 upstream.\n\nThis update is for newer family 15h cpu models from 0x02 to 0x1f.\n\nSigned-off-by: Robert Richter <robert.richter@amd.com>\nAcked-by: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nLink: http://lkml.kernel.org/r/1337337642-1621-1-git-send-email-robert.richter@amd.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthyava/android_kernel_lge_hammerhead/commits/e40ce13c61ab258f65a20c8332c85e648b641046"}]}
{"actor":{"display_login":"anthyava"}}