{"push_id":3075673845,"size":58,"distinct_size":58,"ref":"refs/heads/master","head":"edeca3a769ad28a9477798c3b1d8e0701db728e4","before":"c8ce94b8fe5324aca4c10baeb53dea2d5775a170","commits":[{"sha":"08fd9a82fda86529bb2f2af3c2f7cb657b4d3066","author":{"name":"Andy Shevchenko","email":"74f0c009df510614346aa771cd21959b78cdb413@linux.intel.com"},"message":"usb: dwc3: core: Clean up ULPI device\n\nIf dwc3_core_init_mode() fails with deferred probe,\nnext probe fails on sysfs with\n\nsysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:11.0/dwc3.0.auto/dwc3.0.auto.ulpi'\n\nTo avoid this failure, clean up ULPI device.\n\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/08fd9a82fda86529bb2f2af3c2f7cb657b4d3066"},{"sha":"ba3a51ac32ebcf8d0a54b37f1af268ad8a31c52f","author":{"name":"Thinh Nguyen","email":"8e436f42a8d87f445466a3edb7bd598ad284eedd@synopsys.com"},"message":"usb: dwc3: gadget: Properly check last unaligned/zero chain TRB\n\nCurrent check for the last extra TRB for zero and unaligned transfers\ndoes not account for isoc OUT. The last TRB of the Buffer Descriptor for\nisoc OUT transfers will be retired with HWO=0. As a result, we won't\nreturn early. The req->remaining will be updated to include the BUFSIZ\ncount of the extra TRB, and the actual number of transferred bytes\ncalculation will be wrong.\n\nTo fix this, check whether it's a short or zero packet and the last TRB\nchain bit to return early.\n\nFixes: c6267a51639b (\"usb: dwc3: gadget: align transfers to wMaxPacketSize\")\nCc: <stable@vger.kernel.org>\nSigned-off-by: Thinh Nguyen <thinhn@synopsys.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/ba3a51ac32ebcf8d0a54b37f1af268ad8a31c52f"},{"sha":"781f0766cc41a9dd2e5d118ef4b1d5d89430257b","author":{"name":"Kai-Heng Feng","email":"06af28c154da900e58fef391e9e9415561e1d8ae@canonical.com"},"message":"USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub\n\nDevices connected under Terminus Technology Inc. Hub (1a40:0101) may\nfail to work after the system resumes from suspend:\n[  206.063325] usb 3-2.4: reset full-speed USB device number 4 using xhci_hcd\n[  206.143691] usb 3-2.4: device descriptor read/64, error -32\n[  206.351671] usb 3-2.4: device descriptor read/64, error -32\n\nInfo for this hub:\nT:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=480 MxCh= 4\nD:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1\nP:  Vendor=1a40 ProdID=0101 Rev=01.11\nS:  Product=USB 2.0 Hub\nC:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA\nI:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub\n\nSome expirements indicate that the USB devices connected to the hub are\ninnocent, it's the hub itself is to blame. The hub needs extra delay\ntime after it resets its port.\n\nHence wait for extra delay, if the device is connected to this quirky\nhub.\n\nSigned-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>\nCc: stable <stable@vger.kernel.org>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/781f0766cc41a9dd2e5d118ef4b1d5d89430257b"},{"sha":"a77112577667cbda7c6292c52d909636aef31fd9","author":{"name":"Emmanuel Pescosta","email":"568a74edd1c9b19c817c6a4d2b879882e68e7e75@gmail.com"},"message":"usb: quirks: Add delay-init quirk for Corsair K70 LUX RGB\n\nFollowing on from this patch: https://lkml.org/lkml/2017/11/3/516,\nCorsair K70 LUX RGB keyboards also require the DELAY_INIT quirk to\nstart correctly at boot.\n\nDmesg output:\nusb 1-6: string descriptor 0 read error: -110\nusb 1-6: New USB device found, idVendor=1b1c, idProduct=1b33\nusb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3\nusb 1-6: can't set config #1, error -110\n\nSigned-off-by: Emmanuel Pescosta <emmanuelpescosta099@gmail.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/a77112577667cbda7c6292c52d909636aef31fd9"},{"sha":"deefd24228a172d1b27d4a9adbfd2cdacd60ae64","author":{"name":"Kai-Heng Feng","email":"06af28c154da900e58fef391e9e9415561e1d8ae@canonical.com"},"message":"USB: quirks: Add no-lpm quirk for Raydium touchscreens\n\nRaydium USB touchscreen fails to set config if LPM is enabled:\n[    2.030658] usb 1-8: New USB device found, idVendor=2386, idProduct=3119\n[    2.030659] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0\n[    2.030660] usb 1-8: Product: Raydium Touch System\n[    2.030661] usb 1-8: Manufacturer: Raydium Corporation\n[    7.132209] usb 1-8: can't set config #1, error -110\n\nSame behavior can be observed on 2386:3114.\n\nRaydium claims the touchscreen supports LPM under Windows, so I used\nMicrosoft USB Test Tools (MUTT) [1] to check its LPM status. MUTT shows\nthat the LPM doesn't work under Windows, either. So let's just disable LPM\nfor Raydium touchscreens.\n\n[1] https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-test-tools\n\nSigned-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/deefd24228a172d1b27d4a9adbfd2cdacd60ae64"},{"sha":"f6501f49199097b99e4e263644d88c90d1ec1060","author":{"name":"Mattias Jacobsson","email":"6d030535b083d42a70d5660db6c32bc66da299d8@mok.nu"},"message":"USB: misc: appledisplay: add 20\" Apple Cinema Display\n\nAdd another Apple Cinema Display to the list of supported displays\n\nSigned-off-by: Mattias Jacobsson <2pi@mok.nu>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/f6501f49199097b99e4e263644d88c90d1ec1060"},{"sha":"943126417891372d56aa3fe46295cbf53db31370","author":{"name":"Srinivas Kandagatla","email":"e9a3fcd7365f8e6a430ada3b68b984cb4aaf0c3e@linaro.org"},"message":"slimbus: ngd: remove unnecessary check\n\nSLIM_MSG_CLK_PAUSE_SEQ_FLG is never set in any of the slim core,\nso performing a check in ngd driver is totally unnecessary.\n\nAlso this patch fixes warning about mc field overflow reported\nwith CoverityScan.\n\nMaking clk pause feature optional will be added to slim core in\nnext development cycle.\n\nReported-by: Colin Ian King <colin.king@canonical.com>\nFixes: 917809e2280b (\"slimbus: ngd: Add qcom SLIMBus NGD driver\")\nSigned-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/943126417891372d56aa3fe46295cbf53db31370"},{"sha":"f2ffd4e5bc7b629b312be48fbe3c3a2afbd67e4a","author":{"name":"Bill Kuzeja","email":"e84970cf22ba686f355e08e1895ebbb48355fa8c@stratus.com"},"message":"scsi: qla2xxx: Timeouts occur on surprise removal of QLogic adapter\n\nWhen doing a surprise removal of an adapter, some in flight I/Os can get\nstuck and take a while to complete (they actually time out and are\nretried). We are not handling an early error exit from qla2xxx_eh_abort\nproperly.\n\nFixes: 45235022da99 (\"scsi: qla2xxx: Fix driver unload by shutting down chip\")\nSigned-off-by: Bill Kuzeja <william.kuzeja@stratus.com>\nReviewed-by: Laurence Oberman <loberman@redhat.com>\nAcked-by: Himanshu Madhani <himanshu.madhani@cavium.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/f2ffd4e5bc7b629b312be48fbe3c3a2afbd67e4a"},{"sha":"8e4829c6f7470722c1f5a1dc5769ebe09ef036d6","author":{"name":"Wei Li","email":"0dc5cf8bb9506e514d613eb86bd4592a0b161bef@huawei.com"},"message":"scsi: ufs: Fix hynix ufs bug with quirk on hi36xx SoC\n\nHynix ufs has deviations on hi36xx platform which will result in ufs bursts\ntransfer failures.\n\nTo fix the problem, the Hynix device must set the register\nVS_DebugSaveConfigTime to 0x10, which will set time reference for\nSaveConfigTime is 250 ns. The time reference for SaveConfigTime is 40 ns by\ndefault.\n\nThis patch is necessary to boot on HiKey960 boards that use Hynix UFS chips\n(H28U62301AMR model: hB8aL1).\n\nCc: Vinayak Holikatti <vinholikatti@gmail.com>\nCc: \"James E.J. Bottomley\" <jejb@linux.vnet.ibm.com>\nCc: \"Martin K. Petersen\" <martin.petersen@oracle.com>\nCc: linux-scsi@vger.kernel.org\nSigned-off-by: Wei Li <liwei213@huawei.com>\nSigned-off-by: Dmitry Shmidt <dimitrysh@google.com>\n[jstultz: Forward ported from older code, slight tweak to commit message]\nSigned-off-by: John Stultz <john.stultz@linaro.org>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/8e4829c6f7470722c1f5a1dc5769ebe09ef036d6"},{"sha":"65766ee0bf7fe8b3be80e2e1c3ef54ad59b29476","author":{"name":"Takashi Iwai","email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de"},"message":"ALSA: oss: Use kvzalloc() for local buffer allocations\n\nPCM OSS layer may allocate a few temporary buffers, one for the core\nread/write and another for the conversions via plugins.  Currently\nboth are allocated via vmalloc().  But as the allocation size is\nequivalent with the PCM period size, the required size might be quite\nsmall, depending on the application.\n\nThis patch replaces these vmalloc() calls with kvzalloc() for covering\nsmall period sizes better.  Also, we use \"z\"-alloc variant here for\naddressing the possible uninitialized access reported by syzkaller.\n\nReported-by: syzbot+1cb36954e127c98dd037@syzkaller.appspotmail.com\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/65766ee0bf7fe8b3be80e2e1c3ef54ad59b29476"},{"sha":"f068090426ea8d72c408ebd42953a82a88e2282c","author":{"name":"Mathias Nyman","email":"2d4473c5e67eb83655334d4e9a7757f781607241@linux.intel.com"},"message":"xhci: Fix leaking USB3 shared_hcd at xhci removal\n\nEnsure that the shared_hcd pointer is valid when calling usb_put_hcd()\n\nThe shared_hcd is removed and freed in xhci by first calling\nusb_remove_hcd(xhci->shared_hcd), and later\nusb_put_hcd(xhci->shared_hcd)\n\nAfer commit fe190ed0d602 (\"xhci: Do not halt the host until both HCD have\ndisconnected their devices.\") the shared_hcd was never properly put as\nxhci->shared_hcd was set to NULL before usb_put_hcd(xhci->shared_hcd) was\ncalled.\n\nshared_hcd (USB3) is removed before primary hcd (USB2).\nWhile removing the primary hcd we might need to handle xhci interrupts\nto cleanly remove last USB2 devices, therefore we need to set\nxhci->shared_hcd to NULL before removing the primary hcd to let xhci\ninterrupt handler know shared_hcd is no longer available.\n\nxhci-plat.c, xhci-histb.c and xhci-mtk first create both their hcd's before\nadding them. so to keep the correct reverse removal order use a temporary\nshared_hcd variable for them.\nFor more details see commit 4ac53087d6d4 (\"usb: xhci: plat: Create both\nHCDs before adding them\")\n\nFixes: fe190ed0d602 (\"xhci: Do not halt the host until both HCD have disconnected their devices.\")\nCc: Joel Stanley <joel@jms.id.au>\nCc: Chunfeng Yun <chunfeng.yun@mediatek.com>\nCc: Thierry Reding <treding@nvidia.com>\nCc: Jianguo Sun <sunjianguo1@huawei.com>\nCc: <stable@vger.kernel.org>\nReported-by: Jack Pham <jackp@codeaurora.org>\nTested-by: Jack Pham <jackp@codeaurora.org>\nTested-by: Peter Chen <peter.chen@nxp.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/f068090426ea8d72c408ebd42953a82a88e2282c"},{"sha":"1245374e9b8340fc255fd51b2015173a83050d03","author":{"name":"Mathias Nyman","email":"2d4473c5e67eb83655334d4e9a7757f781607241@linux.intel.com"},"message":"xhci: handle port status events for removed USB3 hcd\n\nAt xhci removal the USB3 hcd (shared_hcd) is removed before the primary\nUSB2 hcd. Interrupts for port status changes may still occur for USB3\nports after the shared_hcd is freed, causing  NULL pointer dereference.\n\nCheck if xhci->shared_hcd is still valid before handing USB3 port events\n\nCc: <stable@vger.kernel.org>\nReported-by: Peter Chen <peter.chen@nxp.com>\nTested-by: Jack Pham <jackp@codeaurora.org>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/1245374e9b8340fc255fd51b2015173a83050d03"},{"sha":"d9193efba84fe4c4aa22a569fade5e6ca971f8af","author":{"name":"Sandeep Singh","email":"8ea51a4fff2b2fb26ac15a8d92df075213f1705a@amd.com"},"message":"xhci: Add check for invalid byte size error when UAS devices are connected.\n\nObserved \"TRB completion code (27)\" error which corresponds to Stopped -\nLength Invalid error(xhci spec section 4.17.4) while connecting USB to\nSATA bridge.\n\nLooks like this case was not considered when the following patch[1] was\ncommitted. Hence adding this new check which can prevent\nthe invalid byte size error.\n\n[1] ade2e3a xhci: handle transfer events without TRB pointer\n\nCc: <stable@vger.kernel.org>\nSigned-off-by: Sandeep Singh <sandeep.singh@amd.com>\ncc: Nehal Shah <Nehal-bakulchandra.Shah@amd.com>\ncc: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/d9193efba84fe4c4aa22a569fade5e6ca971f8af"},{"sha":"958c0bd86075d4ef1c936998deefe1947e539240","author":{"name":"Aaron Ma","email":"6d75ab49fa4401d16749457e532362eb5fdb78e3@canonical.com"},"message":"usb: xhci: fix uninitialized completion when USB3 port got wrong status\n\nRealtek USB3.0 Card Reader [0bda:0328] reports wrong port status on\nCannon lake PCH USB3.1 xHCI [8086:a36d] after resume from S3,\nafter clear port reset it works fine.\n\nSince this device is registered on USB3 roothub at boot,\nwhen port status reports not superspeed, xhci_get_port_status will call\nan uninitialized completion in bus_state[0].\nKernel will hang because of NULL pointer.\n\nRestrict the USB2 resume status check in USB2 roothub to fix hang issue.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Aaron Ma <aaron.ma@canonical.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/958c0bd86075d4ef1c936998deefe1947e539240"},{"sha":"a5baeaeabcca3244782a9b6382ebab6f8a58f583","author":{"name":"Aaron Ma","email":"6d75ab49fa4401d16749457e532362eb5fdb78e3@canonical.com"},"message":"usb: xhci: fix timeout for transition from RExit to U0\n\nThis definition is used by msecs_to_jiffies in milliseconds.\nAccording to the comments, max rexit timeout should be 20ms.\nAlign with the comments to properly calculate the delay.\n\nVerified on Sunrise Point-LP and Cannon Lake.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Aaron Ma <aaron.ma@canonical.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/a5baeaeabcca3244782a9b6382ebab6f8a58f583"},{"sha":"11644a7659529730eaf2f166efaabe7c3dc7af8c","author":{"name":"Cherian, George","email":"e0b5504e0efd7f0b66273c1f97e0a1394aa5871e@cavium.com"},"message":"xhci: Add quirk to workaround the errata seen on Cavium Thunder-X2 Soc\n\nImplement workaround for ThunderX2 Errata-129 (documented in\nCN99XX Known Issues\" available at Cavium support site).\nAs per ThunderX2errata-129, USB 2 device may come up as USB 1\nif a connection to a USB 1 device is followed by another connection to\na USB 2 device, the link will come up as USB 1 for the USB 2 device.\n\nResolution: Reset the PHY after the USB 1 device is disconnected.\nThe PHY reset sequence is done using private registers in XHCI register\nspace. After the PHY is reset we check for the PLL lock status and retry\nthe operation if it fails. From our tests, retrying 4 times is sufficient.\n\nAdd a new quirk flag XHCI_RESET_PLL_ON_DISCONNECT to invoke the workaround\nin handle_xhci_port_status().\n\nCc: stable@vger.kernel.org\nSigned-off-by: George Cherian <george.cherian@cavium.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/11644a7659529730eaf2f166efaabe7c3dc7af8c"},{"sha":"e670de54c813b5bc3672dd1c67871dc60e9206f4","author":{"name":"Dexuan Cui","email":"cd5c9304120b3aad8158bbc6888849d74dea1dde@microsoft.com"},"message":"Drivers: hv: kvp: Fix the recent regression caused by incorrect clean-up\n\nIn kvp_send_key(), we do need call process_ib_ipinfo() if\nmessage->kvp_hdr.operation is KVP_OP_GET_IP_INFO, because it turns out\nthe userland hv_kvp_daemon needs the info of operation, adapter_id and\naddr_family. With the incorrect fc62c3b1977d, the host can't get the\nVM's IP via KVP.\n\nAnd, fc62c3b1977d added a \"break;\", but actually forgot to initialize\nthe key_size/value in the case of KVP_OP_SET, so the default key_size of\n0 is passed to the kvp daemon, and the pool files\n/var/lib/hyperv/.kvp_pool_* can't be updated.\n\nThis patch effectively rolls back the previous fc62c3b1977d, and\ncorrectly fixes the \"this statement may fall through\" warnings.\n\nThis patch is tested on WS 2012 R2 and 2016.\n\nFixes: fc62c3b1977d (\"Drivers: hv: kvp: Fix two \"this statement may fall through\" warnings\")\nSigned-off-by: Dexuan Cui <decui@microsoft.com>\nCc: K. Y. Srinivasan <kys@microsoft.com>\nCc: Stephen Hemminger <sthemmin@microsoft.com>\nSigned-off-by: Haiyang Zhang <haiyangz@microsoft.com>\nCc: <Stable@vger.kernel.org>\nSigned-off-by: K. Y. Srinivasan <kys@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/e670de54c813b5bc3672dd1c67871dc60e9206f4"},{"sha":"fee05f455ceb5c670cbe48e2f9454ebc4a388554","author":{"name":"Gustavo A. R. Silva","email":"beac5f8171fcde5e2ec734cc5d25d03e7362e8de@embeddedor.com"},"message":"drivers/misc/sgi-gru: fix Spectre v1 vulnerability\n\nreq.gid can be indirectly controlled by user-space, hence leading to\na potential exploitation of the Spectre variant 1 vulnerability.\n\nThis issue was detected with the help of Smatch:\n\nvers/misc/sgi-gru/grukdump.c:200 gru_dump_chiplet_request() warn:\npotential spectre issue 'gru_base' [w]\n\nFix this by sanitizing req.gid before calling macro GID_TO_GRU, which\nuses it to index gru_base.\n\nNotice that given that speculation windows are large, the policy is\nto kill the speculation on the first load and not worry if it can be\ncompleted with a dependent load/store [1].\n\n[1] https://marc.info/?l=linux-kernel&m=152449131114778&w=2\n\nCc: stable@vger.kernel.org\nSigned-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/fee05f455ceb5c670cbe48e2f9454ebc4a388554"},{"sha":"7c97301285b62a41d6bceded7d964085fc8cc50f","author":{"name":"Nathan Chancellor","email":"f65d3f2dc139dcfe7b6f0b0a466af3bc5fed8fa7@gmail.com"},"message":"misc: atmel-ssc: Fix section annotation on atmel_ssc_get_driver_data\n\nAfter building the kernel with Clang, the following section mismatch\nwarning appears:\n\nWARNING: vmlinux.o(.text+0x3bf19a6): Section mismatch in reference from\nthe function ssc_probe() to the function\n.init.text:atmel_ssc_get_driver_data()\nThe function ssc_probe() references\nthe function __init atmel_ssc_get_driver_data().\nThis is often because ssc_probe lacks a __init\nannotation or the annotation of atmel_ssc_get_driver_data is wrong.\n\nRemove __init from atmel_ssc_get_driver_data to get rid of the mismatch.\n\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/7c97301285b62a41d6bceded7d964085fc8cc50f"},{"sha":"0749aa25af82c690395a96e799cd2c6e54c459cf","author":{"name":"Srinivas Kandagatla","email":"e9a3fcd7365f8e6a430ada3b68b984cb4aaf0c3e@linaro.org"},"message":"nvmem: core: fix regression in of_nvmem_cell_get()\n\nNVMEM DT support seems to be totally broken after\ncommit e888d445ac33 (\"nvmem: resolve cells from DT at registration time\")\nFix this!\n\nIndex used in of_nvmem_cell_get() to find cell is specific to\nconsumer, It can not be used for searching the cell in provider.\nUse device_node instead of this to find the matching cell in device\ntree case.\n\nFixes: e888d445ac33 (\"nvmem: resolve cells from DT at registration time\")\nReported-by: Niklas Cassel <niklas.cassel@linaro.org>\nSigned-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>\nTested-by: Niklas Cassel <niklas.cassel@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/huzq85/linux-fork/commits/0749aa25af82c690395a96e799cd2c6e54c459cf"}]}
{"actor":{"display_login":"huzq85"}}