GitHub PushEvent at 2014-01-29 16:42:31
Repository: grakernel-tuna
Actor: Grarak
Payload: {"shas":[["233ae3388093ea4cf64a0ba88a824745f1b9762a","645ca7d3a8d3d4f60557176cd361ea8351edc32b@chello.nl","sched: clock wrap bug in 2.6.35-stable kills scheduling\n\nOn Mon, 2012-06-25 at 11:45 +0200, Peter Zijlstra wrote:\n> On Sun, 2012-06-24 at 19:32 +0200, Thomas Lange wrote:\n> > Bug was introduced in 2.6.35.12 and is still present in linux-2.6.35.y HEAD.\n>\n> Ok, so nobody cares about that.. what does something recent like 3.5-rc4\n> do?\n>\n> If that's fixed, find the patch that fixes it. If not, we'll have a\n> look.\n\nIf anything, I think something like the below ought to cure things.","Peter Zijlstra",true],["0d0ddbe9397af1ef30f1ac4bd76b9147942c4218","e42d9ed0b11728120d1c5543054540de954900bd@ti.com","USB: gadget: f_mtp: fix send ZLP packet algorithm.\n\nUSB: gadget: f_mtp: fix send ZLP packet algorithm.\n\nIf size of the data that sent from MTP-device to computer is a multiple of\nwMaxPacketSize (usb endpoint) then at the end of transfer device must\nsend ZLP packet. Previously in f_mtp module a variable 'maxpacket' that\nused to send ZLP packet was always equal to 512. For USB2.0 wMaxPacketSize\nequals 512 but for USB1.1 wMaxPacketSize can be 64, 32, 16 or 8. Now variable\n'maxpacket' contains real value of wMaxPacketSize in all USB modes and ZLP\npacket is sent correctly for USB1.1.\n\nChange-Id: I75606c954119dea2a76d955849a47208df0d2db0\nSigned-off-by: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@ti.com>","Oleksandr Dmytryshyn",true],["6537d8e58b8b2bf6434739819deb3fadc644d018","1100d3bbb092e6691a138903fe8ea324306d03ea@android.com","OMAP4: dss2: make s6e8aa0 pixel_clock reflect reality\n\nChange-Id: I20c7c0853275edd69497f442cb2226955b98898a\nSigned-off-by: Erik Gilling <konkers@android.com>","Erik Gilling",true],["a969b729760df7cf125dfe19e88ffa9dfe6249e8","5b1a755a6b1799d96d2e1f98e16b285f5f690241@google.com","net: wireless: bcmdhd: Set probe_resp.timestamp value to scan results\n\nSigned-off-by: Dmitry Shmidt <dimitrysh@google.com>","Dmitry Shmidt",true],["83d3b1739927c6b38ae22bf3f022348447e8a96b","1a2f18c7887fc8d384193bb926e616097dea5b69@google.com","HACK: input: mms_ts: Log a touch event after driver enable.\n\nSome people are complaining that after a resume, they are not getting\ntouch screen events.\nThis change only logs 1 event after each enable.\n\nBug: 6258051\nChange-Id: Iad508befde6fafec1b454aa334f8d47a3750a3eb\nSigned-off-by: JP Abgrall <jpa@google.com>","JP Abgrall",true],["b3a0bbe1390c77762b69a1767262ee2fe98f65ef","c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","OMAP3+: ABB: make the pre and post scale decision based off Vnom\n\nCurrently the ABB LDO prescale and post scale configurations are\ndone based off voltdm_scale. However when Vsr(SR adjusted voltage)\nof the current OPP is the same as Vnom(nominal voltage) of the new\nOPP, this results in voltdm_scale not being called.\n\nThis has a side-effect of prescale and postscale of ABB not being\ninvoked either. In case where the new OPP requires FBB, this will\nresult in device failure.\n\nThe right procedure is to move the prescale and postscale notifier\nout of the voltage scale API, instead have it on top of dvfs path\nand depend on nominal voltage scaling direction to give a proper\ntrigger on need basis.\n\nNOTE: ABB prescale is skipped in pm.c initial configuration to\ntake care of various types of bad and correct bootloader\nconfiguration.\n\nChange-Id: Ie953f515ab6182d6fa9be85d0ea83228db63d969\nSigned-off-by: Nishanth Menon <nm@ti.com>\n\nConflicts:\n\n\tarch/arm/mach-omap2/dvfs.c","faux123",true],["b5734f1110320709a032a86499a14e9c3564506f","1a2f18c7887fc8d384193bb926e616097dea5b69@google.com","Revert \"HACK: input: mms_ts: Log a touch event after driver enable.\"\n\nThis reverts commit 4ff08e36fda8c309c5ed320c7cd2546cb88f752c\n\nGet rid of the debugging for the release.\n\nSigned-off-by: JP Abgrall <jpa@google.com>\nChange-Id: I4dd4cf62f2c574db80c70210771a9bed11dedcab","JP Abgrall",true],["50a2a8e6b9f4695e9846fd4afd37d5da257c126b","4f38951e22882ba08951a3332be9e3e19643b51b@broadcom.com","net: wireless: bcmdhd: Fix WPS PBC overlap failure\n\nSigned-off-by: Dmitry Shmidt <dimitrysh@google.com>","Neeraj Kumar Garg",true],["71989ad624abc2cb26f216dd6c27e87fcefdace7","c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","defconfig: JellyBean initial defconfig","faux123",true],["81653a9a9fa2417f553f9d88a91c10ff0c89a4b8","c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","Revert \"OMAP3+: DVFS: ensure proper volt config if curr_volt==new_volt\"\n\nThis reverts commit 225b3f6ff1638f7ebf8ab40a7dfd3694ded6eaae.","faux123",true],["67222e5a9ee4530fa92b312beeb0f39c7c29e62e","c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","Revert \"OMAP3+: ABB: make the pre and post scale decision based off Vnom\"\n\nThis reverts commit a2ec14bd770d35489fdea69b29a0f8489a34a6e1.","faux123",true],["7ee74a28660c2c1a4460b9321db7e203405baaeb","c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","defconfig: small update for JB kernel","faux123",true],["2dcf94eda3ebf59b922fb2a7bbbce56057ba76c2","c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","Revert \"OMAPDSS: CEC: Adding HDMI CEC support\"\n\nThis reverts commit dde55de2bbee46514e31dd3aa4db0fd9fb3fedf6.","faux123",true],["4e5c0819cc2ee269f5df2235ba8e0d2a24d3bd0c","c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","Revert \"OMAPDSS: CEC: Add callback to CEC driver on HDMI HPD\"\n\nThis reverts commit 6fd2e4089751a24386f6e51d04ee33fd0393847e.","faux123",true],["6e2daf68ad397914505d025327ebb3b55c7d0f3a","c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","Revert \"OMAPDSS: CEC: Physical address discovery form edid\"\n\nThis reverts commit 1b1fd9110ea8607c55384a0f794fc817cb958dbd.","faux123",true],["a1b97a6292f3884273d67e8dec9e867ad74e017e","c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","defconfig: JB kernel defconfig refresh based on AOSP","faux123",true]],"size":16,"ref":"refs/heads/4.4","head":"a1b97a6292f3884273d67e8dec9e867ad74e017e"}