{"push_id":1335722261,"size":4,"distinct_size":4,"ref":"refs/heads/LA.HB.1.3.1","head":"0f2fba71666f01d34a4961b9ea548f8b0e75b2b5","before":"57446093d828ca14bea2322f824e98231c1c7027","commits":[{"sha":"15e9b8817d64c9502831013f77221db3ecfb1f56","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"perf: Tighten (and fix) the grouping condition\n\nThe fix from 9fc81d87420d (\"perf: Fix events installation during\nmoving group\") was incomplete in that it failed to recognise that\ncreating a group with events for different CPUs is semantically\nbroken -- they cannot be co-scheduled.\n\nFurthermore, it leads to real breakage where, when we create an event\nfor CPU Y and then migrate it to form a group on CPU X, the code gets\nconfused where the counter is programmed -- triggered in practice\nas well by me via the perf fuzzer.\n\nFix this by tightening the rules for creating groups. Only allow\ngrouping of counters that can be co-scheduled in the same context.\nThis means for the same task and/or the same cpu.\n\nChange-Id: I01d7b24b44fff039e72c80cca7f70158fa354470\nFixes: 9fc81d87420d (\"perf: Fix events installation during moving group\")\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Arnaldo Carvalho de Melo <acme@kernel.org>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nLink: http://lkml.kernel.org/r/20150123125834.090683288@infradead.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Kamal Mostafa <kamal@canonical.com>\nGit-commit: c3c87e770458aa004bd7ed3f29945ff436fd6511\nGit-repo: http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git\nSigned-off-by: Patrick Fay <pfay@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/myfluxi/android_kernel_oneplus_msm8996/commits/15e9b8817d64c9502831013f77221db3ecfb1f56"},{"sha":"1426a32d4bdb581b870217ac2db5b2b89e02ac24","author":{"name":"Srinivas Girigowda","email":"a31baf9905f545cc28ca3ed31e582f4e1f5462f1@codeaurora.org"},"message":"qcacld-2.0: Optimize WoW Wakelock usage in Runtime PM\n\nFW sends NACK for WOW command to indicate Host to abort on going\nsuspend. Host prevents suspend by holding a wakelock for 1sec.\nThe wakelock prevents APPS supsend, but doesn't have impact on\nRuntime PM. Hence Skip Holding Wakelock when NACK is recieved\nin Runtime PM.\n\nAnd Log the runtime stats when link resume fails.\n\nChange-Id: I6d9385565c6d06a082e226d5211c733d124bd3a7\nCRs-Fixed: 1053252\nBug: 31062353\nSigned-off-by: Srinivas Girigowda <sgirigow@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/myfluxi/android_kernel_oneplus_msm8996/commits/1426a32d4bdb581b870217ac2db5b2b89e02ac24"},{"sha":"a3c81d3be31e863bad44a1d8b13538ba23ea51e3","author":{"name":"Srinivas Girigowda","email":"a31baf9905f545cc28ca3ed31e582f4e1f5462f1@codeaurora.org"},"message":"qcacld-2.0: Prevent NOC/Link Access in resume when Link is down\n\nPCIe link training failure will not be indicated to cnss client driver\nas a link down indication.\n\nIn System/Runtime PM resume callbacks, client driver will access the target\nregisters results in L2 errors.\n\nFix it by ensuring the PCIe link resume training is completed by reading\nconfig space device-id.\n\nChange-Id: I8be902330215cf3c8cb0700e6f0da5b69e274c96\nCRs-Fixed: 1052965\nBug: 31062353\nSigned-off-by: Srinivas Girigowda <sgirigow@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/myfluxi/android_kernel_oneplus_msm8996/commits/a3c81d3be31e863bad44a1d8b13538ba23ea51e3"},{"sha":"0f2fba71666f01d34a4961b9ea548f8b0e75b2b5","author":{"name":"fluxi","email":"95ab61bb01957fc548ef82d227666a28af3268a6@arcor.de"},"message":"qcacld-2.0: Fix compilation\n\nWe are missing the wrapper function for this.\n\nChange-Id: Iad06ec6d7e75011692b8e573ae07d676d78ad28d","distinct":true,"url":"https://api.github.com/repos/myfluxi/android_kernel_oneplus_msm8996/commits/0f2fba71666f01d34a4961b9ea548f8b0e75b2b5"}]}
{"actor":{"display_login":"myfluxi"}}