{"push_id":1135140285,"size":229,"distinct_size":229,"ref":"refs/heads/upstream","head":"cedfdb0c56bc60d079385d66e1598f06264a58c7","before":"2fff0eba3854e129b8209f9e51811dc1485d7c38","commits":[{"sha":"1ee1c44323a192a7ecc698e979b0323473e098cc","author":{"name":"David Dillow","email":"b4cea4bb99b2bfe98580e8a1404151e1fa946999@thedillows.org"},"message":"media: cx231xx: don't DMA to random addresses\n\ncommit a7deca6fa79d5c65575532e780f3c93f6bf8ddad upstream.\n\nCommit 7a6f6c29d264cdd2fe0eb3d923217eed5f0ad134 (cx231xx: use\nURB_NO_TRANSFER_DMA_MAP) was intended to avoid mapping the DMA buffer\nfor URB twice. This works for the URBs allocated with usb_alloc_urb(),\nas those are allocated from cohernent DMA pools, but the flag was also\nadded for the VBI and audio URBs, which have a manually allocated area.\nThis leaves the random trash in the structure after allocation as the\nDMA address, corrupting memory and preventing VBI and audio from\nworking. Letting the USB core map the buffers solves the problem.\n\nSigned-off-by: David Dillow <dave@thedillows.org>\nCc: Sri Deevi <srinivasa.deevi@conexant.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/1ee1c44323a192a7ecc698e979b0323473e098cc"},{"sha":"51a894fc7ed69497e39f408a4e043dce9aef0c5d","author":{"name":"Jean Delvare","email":"f1ede6b77af31eb13e1c412cb29d4c7fa9f0ff87@linux-fr.org"},"message":"hwmon: (it87) Preserve configuration register bits on init\n\ncommit 41002f8dd5938d5ad1d008ce5bfdbfe47fa7b4e8 upstream.\n\nWe were accidentally losing one bit in the configuration register on\ndevice initialization. It was reported to freeze one specific system\nright away. Properly preserve all bits we don't explicitly want to\nchange in order to prevent that.\n\nReported-by: Stevie Trujillo <stevie.trujillo@gmail.com>\nSigned-off-by: Jean Delvare <khali@linux-fr.org>\nReviewed-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/51a894fc7ed69497e39f408a4e043dce9aef0c5d"},{"sha":"82245dd02a4650d953b28991a65258730b5f1d41","author":{"name":"Jeff Moyer","email":"68b5f047f1723a3511b0e5437220489b2cff9ae5@redhat.com"},"message":"block: fix infinite loop in __getblk_slow\n\ncommit 91f68c89d8f35fe98ea04159b9a3b42d0149478f upstream.\n\nCommit 080399aaaf35 (\"block: don't mark buffers beyond end of disk as\nmapped\") exposed a bug in __getblk_slow that causes mount to hang as it\nloops infinitely waiting for a buffer that lies beyond the end of the\ndisk to become uptodate.\n\nThe problem was initially reported by Torsten Hilbrich here:\n\n    https://lkml.org/lkml/2012/6/18/54\n\nand also reported independently here:\n\n    http://www.sysresccd.org/forums/viewtopic.php?f=13&t=4511\n\nand then Richard W.M.  Jones and Marcos Mello noted a few separate\nbugzillas also associated with the same issue.  This patch has been\nconfirmed to fix:\n\n    https://bugzilla.redhat.com/show_bug.cgi?id=835019\n\nThe main problem is here, in __getblk_slow:\n\n        for (;;) {\n                struct buffer_head * bh;\n                int ret;\n\n                bh = __find_get_block(bdev, block, size);\n                if (bh)\n                        return bh;\n\n                ret = grow_buffers(bdev, block, size);\n                if (ret < 0)\n                        return NULL;\n                if (ret == 0)\n                        free_more_memory();\n        }\n\n__find_get_block does not find the block, since it will not be marked as\nmapped, and so grow_buffers is called to fill in the buffers for the\nassociated page.  I believe the for (;;) loop is there primarily to\nretry in the case of memory pressure keeping grow_buffers from\nsucceeding.  However, we also continue to loop for other cases, like the\nblock lying beond the end of the disk.  So, the fix I came up with is to\nonly loop when grow_buffers fails due to memory allocation issues\n(return value of 0).\n\nThe attached patch was tested by myself, Torsten, and Rich, and was\nfound to resolve the problem in call cases.\n\nSigned-off-by: Jeff Moyer <jmoyer@redhat.com>\nReported-and-Tested-by: Torsten Hilbrich <torsten.hilbrich@secunet.com>\nTested-by: Richard W.M. Jones <rjones@redhat.com>\nReviewed-by: Josh Boyer <jwboyer@redhat.com>\n[ Jens is on vacation, taking this directly  - Linus ]\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/SandPox/android_kernel_samsung_kyleproxx/commits/82245dd02a4650d953b28991a65258730b5f1d41"},{"sha":"620a8292df08bb7602588a0c332c62ea1f446fc1","author":{"name":"Santosh Nayak","email":"a789f081b1d065663b11162c56931def30cdde56@gmail.com"},"message":"media: dvb-core: Release semaphore on error path dvb_register_device()\n\ncommit 82163edcdfa4eb3d74516cc8e9f38dd3d039b67d upstream.\n\nThere is a missing \"up_write()\" here. Semaphore should be released\nbefore returning error value.\n\nSigned-off-by: Santosh Nayak <santoshprasadnayak@gmail.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/620a8292df08bb7602588a0c332c62ea1f446fc1"},{"sha":"a4d67848f0f4ffc7748fdb257f8c55d1c0f055fb","author":{"name":"Herton Ronaldo Krzesinski","email":"6101089def9d1c34f51daa442462b3863671e736@canonical.com"},"message":"mtd: nandsim: don't open code a do_div helper\n\ncommit 596fd46268634082314b3af1ded4612e1b7f3f03 upstream.\n\nWe don't need to open code the divide function, just use div_u64 that\nalready exists and do the same job. While this is a straightforward\nclean up, there is more to that, the real motivation for this.\n\nWhile building on a cross compiling environment in armel, using gcc\n4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5), I was getting the following build\nerror:\n\nERROR: \"__aeabi_uldivmod\" [drivers/mtd/nand/nandsim.ko] undefined!\n\nAfter investigating with objdump and hand built assembly version\ngenerated with the compiler, I narrowed __aeabi_uldivmod as being\ngenerated from the divide function. When nandsim.c is built with\n-fno-inline-functions-called-once, that happens when\nCONFIG_DEBUG_SECTION_MISMATCH is enabled, the do_div optimization in\narch/arm/include/asm/div64.h doesn't work as expected with the open\ncoded divide function: even if the do_div we are using doesn't have a\nconstant divisor, the compiler still includes the else parts of the\noptimized do_div macro, and translates the divisions there to use\n__aeabi_uldivmod, instead of only calling __do_div_asm -> __do_div64 and\noptimizing/removing everything else out.\n\nSo to reproduce, gcc 4.6 plus CONFIG_DEBUG_SECTION_MISMATCH=y and\nCONFIG_MTD_NAND_NANDSIM=m should do it, building on armel.\n\nAfter this change, the compiler does the intended thing even with\n-fno-inline-functions-called-once, and optimizes out as expected the\nconstant handling in the optimized do_div on arm. As this also avoids a\nbuild issue, I'm marking for Stable, as I think is applicable for this\ncase.\n\nSigned-off-by: Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com>\nAcked-by: Nicolas Pitre <nico@linaro.org>\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nSigned-off-by: David Woodhouse <David.Woodhouse@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/a4d67848f0f4ffc7748fdb257f8c55d1c0f055fb"},{"sha":"015a0c1600ae60876d0718eb7783aacc360138a3","author":{"name":"NeilBrown","email":"2d905a3497a379bccf401a15c6d441d61e66863c@suse.de"},"message":"md/raid1: fix use-after-free bug in RAID1 data-check code.\n\ncommit 2d4f4f3384d4ef4f7c571448e803a1ce721113d5 upstream.\n\nThis bug has been present ever since data-check was introduce\nin 2.6.16.  However it would only fire if a data-check were\ndone on a degraded array, which was only possible if the array\nhas 3 or more devices.  This is certainly possible, but is quite\nuncommon.\n\nSince hot-replace was added in 3.3 it can happen more often as\nthe same condition can arise if not all possible replacements are\npresent.\n\nThe problem is that as soon as we submit the last read request, the\n'r1_bio' structure could be freed at any time, so we really should\nstop looking at it.  If the last device is being read from we will\nstop looking at it.  However if the last device is not due to be read\nfrom, we will still check the bio pointer in the r1_bio, but the\nr1_bio might already be free.\n\nSo use the read_targets counter to make sure we stop looking for bios\nto submit as soon as we have submitted them all.\n\nThis fix is suitable for any -stable kernel since 2.6.16.\n\nReported-by: Arnold Schulz <arnysch@gmx.net>\nSigned-off-by: NeilBrown <neilb@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/015a0c1600ae60876d0718eb7783aacc360138a3"},{"sha":"7d17b9b3db75139cfcd8ab89fbfe9afce245e44c","author":{"name":"Todd Poynor","email":"029db66065441d2248abc6ad98d5a188dfd3826a@google.com"},"message":"ARM: SAMSUNG: fix race in s3c_adc_start for ADC\n\ncommit 8265981bb439f3ecc5356fb877a6c2a6636ac88a upstream.\n\nChecking for adc->ts_pend already claimed should be done with the\nlock held.\n\nSigned-off-by: Todd Poynor <toddpoynor@google.com>\nAcked-by: Ben Dooks <ben-linux@fluff.org>\nSigned-off-by: Kukjin Kim <kgene.kim@samsung.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/7d17b9b3db75139cfcd8ab89fbfe9afce245e44c"},{"sha":"b899048f0e0b1104e0d7c64fb9eb1a927bc8eb70","author":{"name":"Bob Moore","email":"501acddd9011c8588884986035dc215c5dbc831d@intel.com"},"message":"ACPICA: Fix possible fault in return package object repair code\n\ncommit 46befd6b38d802dfc5998e7d7938854578b45d9d upstream.\n\nFixes a problem that can occur when a lone package object is\nwrapped with an outer package object in order to conform to\nthe ACPI specification. Can affect these predefined names:\n_ALR,_MLS,_PSS,_TRT,_TSS,_PRT,_HPX,_DLM,_CSD,_PSD,_TSD\n\nhttps://bugzilla.kernel.org/show_bug.cgi?id=44171\n\nThis problem was introduced in 3.4-rc1 by commit\n6a99b1c94d053b3420eaa4a4bc8b2883dd90a2f9\n(ACPICA: Object repair code: Support to add Package wrappers)\n\nReported-by: Vlastimil Babka <caster@gentoo.org>\nSigned-off-by: Bob Moore <robert.moore@intel.com>\nSigned-off-by: Lin Ming <ming.m.lin@intel.com>\nSigned-off-by: Len Brown <len.brown@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/b899048f0e0b1104e0d7c64fb9eb1a927bc8eb70"},{"sha":"d14ddff392bb585b081a8b44888a3ae10b64402c","author":{"name":"Thomas Renninger","email":"d31422578a6cab2601b0e74ce48b4096ff7d12e3@suse.de"},"message":"cpufreq / ACPI: Fix not loading acpi-cpufreq driver regression\n\ncommit c4686c71a9183f76e3ef59098da5c098748672f6 upstream.\n\nCommit d640113fe80e45ebd4a5b420b introduced a regression on SMP\nsystems where the processor core with ACPI id zero is disabled\n(typically should be the case because of hyperthreading).\nThe regression got spread through stable kernels.\nOn 3.0.X it got introduced via 3.0.18.\n\nSuch platforms may be rare, but do exist.\nLook out for a disabled processor with acpi_id 0 in dmesg:\nACPI: LAPIC (acpi_id[0x00] lapic_id[0x10] disabled)\n\nThis problem has been observed on a:\nHP Proliant BL280c G6 blade\n\nThis patch restricts the introduced workaround to platforms\nwith nr_cpu_ids <= 1.\n\nSigned-off-by: Thomas Renninger <trenn@suse.de>\nSigned-off-by: Rafael J. Wysocki <rjw@sisk.pl>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/d14ddff392bb585b081a8b44888a3ae10b64402c"},{"sha":"435021dbecc10c8d8b6e378618a97203532ecb3b","author":{"name":"Takashi Iwai","email":"dd0a9a4ae370c51e6d7099900a4bf6656524e055@suse.de"},"message":"intel_ips: blacklist HP ProBook laptops\n\ncommit 88ca518b0bb4161e5f20f8a1d9cc477cae294e54 upstream.\n\nintel_ips driver spews the warning message\n  \"ME failed to update for more than 1s, likely hung\"\nat each second endlessly on HP ProBook laptops with IronLake.\n\nAs this has never worked, better to blacklist the driver for now.\n\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Matthew Garrett <mjg@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/435021dbecc10c8d8b6e378618a97203532ecb3b"},{"sha":"5ee6daa69a4cfa9bb5545d3fd51184caac192088","author":{"name":"Stanislaw Gruszka","email":"dde6c4452d7e66c518d60d02e63ca2a84b9a50f2@redhat.com"},"message":"rt2x00usb: fix indexes ordering on RX queue kick\n\ncommit efd821182cec8c92babef6e00a95066d3252fda4 upstream.\n\nOn rt2x00_dmastart() we increase index specified by Q_INDEX and on\nrt2x00_dmadone() we increase index specified by Q_INDEX_DONE. So entries\nbetween Q_INDEX_DONE and Q_INDEX are those we currently process in the\nhardware. Entries between Q_INDEX and Q_INDEX_DONE are those we can\nsubmit to the hardware.\n\nAccording to that fix rt2x00usb_kick_queue(), as we need to submit RX\nentries that are not processed by the hardware. It worked before only\nfor empty queue, otherwise was broken.\n\nNote that for TX queues indexes ordering are ok. We need to kick entries\nthat have filled skb, but was not submitted to the hardware, i.e.\nstarted from Q_INDEX_DONE and have ENTRY_DATA_PENDING bit set.\n\nFrom practical standpoint this fixes RX queue stall, usually reproducible\nin AP mode, like for example reported here:\nhttps://bugzilla.redhat.com/show_bug.cgi?id=828824\n\nReported-and-tested-by: Franco Miceli <fmiceli@plan.ceibal.edu.uy>\nReported-and-tested-by: Tom Horsley <horsley1953@gmail.com>\nSigned-off-by: Stanislaw Gruszka <sgruszka@redhat.com>\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/SandPox/android_kernel_samsung_kyleproxx/commits/5ee6daa69a4cfa9bb5545d3fd51184caac192088"},{"sha":"f83bde6d545186f20a94e4fd16b6a7ea4b462791","author":{"name":"Tushar Dave","email":"5fd31bff9e56176dfb43df72b02ecb5b706733f2@intel.com"},"message":"e1000e: Correct link check logic for 82571 serdes\n\ncommit d0efa8f23a644f7cb7d1f8e78dd9a223efa412a3 upstream.\n\nSYNCH bit and IV bit of RXCW register are sticky. Before examining these bits,\nRXCW should be read twice to filter out one-time false events and have correct\nvalues for these bits. Incorrect values of these bits in link check logic can\ncause weird link stability issues if auto-negotiation fails.\n\nReported-by: Dean Nelson <dnelson@redhat.com>\nSigned-off-by: Tushar Dave <tushar.n.dave@intel.com>\nReviewed-by: Bruce Allan <bruce.w.allan@intel.com>\nTested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>\nSigned-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/f83bde6d545186f20a94e4fd16b6a7ea4b462791"},{"sha":"aba3374bd8f0031f9d8ceb9f233da457253e487a","author":{"name":"Stanislaw Gruszka","email":"dde6c4452d7e66c518d60d02e63ca2a84b9a50f2@redhat.com"},"message":"iwlegacy: always monitor for stuck queues\n\ncommit c2ca7d92ed4bbd779516beb6eb226e19f7f7ab0f upstream.\n\nThis is iwlegacy version of:\n\ncommit 342bbf3fee2fa9a18147e74b2e3c4229a4564912\nAuthor: Johannes Berg <johannes.berg@intel.com>\nDate:   Sun Mar 4 08:50:46 2012 -0800\n\n    iwlwifi: always monitor for stuck queues\n\n    If we only monitor while associated, the following\n    can happen:\n     - we're associated, and the queue stuck check\n       runs, setting the queue \"touch\" time to X\n     - we disassociate, stopping the monitoring,\n       which leaves the time set to X\n     - almost 2s later, we associate, and enqueue\n       a frame\n     - before the frame is transmitted, we monitor\n       for stuck queues, and find the time set to\n       X, although it is now later than X + 2000ms,\n       so we decide that the queue is stuck and\n       erroneously restart the device\n\nSigned-off-by: Stanislaw Gruszka <sgruszka@redhat.com>\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/SandPox/android_kernel_samsung_kyleproxx/commits/aba3374bd8f0031f9d8ceb9f233da457253e487a"},{"sha":"748896a9537ee8288e8d514da14b759eeff2e7b8","author":{"name":"Emmanuel Grumbach","email":"8b9b3ed0afbc1fa5fc02c3dc29b7819d4e9d8433@intel.com"},"message":"iwlegacy: don't mess up the SCD when removing a key\n\ncommit b48d96652626b315229b1b82c6270eead6a77a6d upstream.\n\nWhen we remove a key, we put a key index which was supposed\nto tell the fw that we are actually removing the key. But\ninstead the fw took that index as a valid index and messed\nup the SRAM of the device.\n\nThis memory corruption on the device mangled the data of\nthe SCD. The impact on the user is that SCD queue 2 got\nstuck after having removed keys.\n\nReported-by: Paul Bolle <pebolle@tiscali.nl>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Stanislaw Gruszka <sgruszka@redhat.com>\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/SandPox/android_kernel_samsung_kyleproxx/commits/748896a9537ee8288e8d514da14b759eeff2e7b8"},{"sha":"14c9a11ffb5b3903b8937ca9df7009c983947465","author":{"name":"Federico Fuga","email":"998bd9ace17a38fcad0fad0a838ce8d9ef4e406c@studiofuga.com"},"message":"rpmsg: fix dependency on initialization order\n\ncommit 9634252617441991b01dacaf4040866feecaf36f upstream.\n\nWhen rpmsg drivers are built into the kernel, they must not initialize\nbefore the rpmsg bus does, otherwise they'd trigger a BUG() in\ndrivers/base/driver.c line 169 (driver_register()).\n\nTo fix that, and to stop depending on arbitrary linkage ordering of\nthose built-in rpmsg drivers, we make the rpmsg bus initialize at\nsubsys_initcall.\n\nSigned-off-by: Federico Fuga <fuga@studiofuga.com>\n[ohad: rewrite the commit log]\nSigned-off-by: Ohad Ben-Cohen <ohad@wizery.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SandPox/android_kernel_samsung_kyleproxx/commits/14c9a11ffb5b3903b8937ca9df7009c983947465"},{"sha":"6283e1080b67d0534047a3649b83f76ad9bed4de","author":{"name":"Eliad Peller","email":"684fb8683f326e95c8317af28b8e3c8e2d5c75ec@wizery.com"},"message":"mac80211: destroy assoc_data correctly if assoc fails\n\ncommit 10a9109f2705fdc3caa94d768b2559587a9a050c upstream.\n\nIf association failed due to internal error (e.g. no\nsupported rates IE), we call ieee80211_destroy_assoc_data()\nwith assoc=true, while we actually reject the association.\n\nThis results in the BSSID not being zeroed out.\n\nAfter passing assoc=false, we no longer have to call\nsta_info_destroy_addr() explicitly. While on it, move\nthe \"associated\" message after the assoc_success check.\n\nSigned-off-by: Eliad Peller <eliad@wizery.com>\nReviewed-by: Johannes Berg <johannes@sipsolutions.net>\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/SandPox/android_kernel_samsung_kyleproxx/commits/6283e1080b67d0534047a3649b83f76ad9bed4de"},{"sha":"c93f4417301a32f5ad3cd03be1d031beb1deee8f","author":{"name":"Deepak Sikri","email":"7c29e93ea5a52d116741813568715c5912741a2f@st.com"},"message":"stmmac: Fix for nfs hang on multiple reboot\n\ncommit 8e83989106562326bfd6aaf92174fe138efd026b upstream.\n\nIt was observed that during multiple reboots nfs hangs. The status of\nreceive descriptors shows that all the descriptors were in control of\nCPU, and none were assigned to DMA.\nAlso the DMA status register confirmed that the Rx buffer is\nunavailable.\n\nThis patch adds the fix for the same by adding the memory barriers to\nascertain that the all instructions before enabling the Rx or Tx DMA are\ncompleted which involves the proper setting of the ownership bit in DMA\ndescriptors.\n\nSigned-off-by: Deepak Sikri <deepak.sikri@st.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/SandPox/android_kernel_samsung_kyleproxx/commits/c93f4417301a32f5ad3cd03be1d031beb1deee8f"},{"sha":"fe8c06a4726f82cc89654d00bd2a411dcb2ac5cd","author":{"name":"Eric W. Biederman","email":"e4ccc9f9b54eebd6cb8fc7643b8083f628b68ff2@xmission.com"},"message":"bonding: debugfs and network namespaces are incompatible\n\ncommit 96ca7ffe748bf91f851e6aa4479aa11c8b1122ba upstream.\n\nThe bonding debugfs support has been broken in the presence of network\nnamespaces since it has been added.  The debugfs support does not handle\nmultiple bonding devices with the same name in different network\nnamespaces.\n\nI haven't had any bug reports, and I'm not interested in getting any.\nDisable the debugfs support when network namespaces are enabled.\n\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.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/SandPox/android_kernel_samsung_kyleproxx/commits/fe8c06a4726f82cc89654d00bd2a411dcb2ac5cd"},{"sha":"ed02606b5ceefa4bab656865be114362f55d44bc","author":{"name":"Eric W. Biederman","email":"e4ccc9f9b54eebd6cb8fc7643b8083f628b68ff2@xmission.com"},"message":"bonding: Manage /proc/net/bonding/ entries from the netdev events\n\ncommit a64d49c3dd504b685f9742a2f3dcb11fb8e4345f upstream.\n\nIt was recently reported that moving a bonding device between network\nnamespaces causes warnings from /proc.  It turns out after the move we\nwere trying to add and to remove the /proc/net/bonding entries from the\nwrong network namespace.\n\nMove the bonding /proc registration code into the NETDEV_REGISTER and\nNETDEV_UNREGISTER events where the proc registration and unregistration\nwill always happen at the right time.\n\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.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/SandPox/android_kernel_samsung_kyleproxx/commits/ed02606b5ceefa4bab656865be114362f55d44bc"},{"sha":"46460b276089ac5781dbb5b2017697d32f7cab96","author":{"name":"Henrik Rydberg","email":"94f2dcc1c12a251a3cb3840b0bbdf75ad98cee45@euromail.se"},"message":"Input: bcm5974 - Add support for 2012 MacBook Pro Retina\n\ncommit 3dde22a98e94eb18527f0ff0068fb2fb945e58d4 upstream.\n\nAdd support for the 15'' MacBook Pro Retina model (MacBookPro10,1).\n\nPatch originally written by clipcarl (forums.opensuse.org).\n\nSigned-off-by: Henrik Rydberg <rydberg@euromail.se>\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/SandPox/android_kernel_samsung_kyleproxx/commits/46460b276089ac5781dbb5b2017697d32f7cab96"}]}
{"actor":{"display_login":"SandPox"}}