{"push_id":4481366675,"size":1000,"distinct_size":9,"ref":"refs/heads/submit/ata-platform_iomap_resource","head":"19a388797f3e59b70c22db9473dc9b7fecb78533","before":"baf794abe3751c43ea5420ea9781b27e71f894c4","commits":[{"sha":"19e6317d24c25ee737c65d1ffb7483bdda4bb54a","author":{"name":"Pete Zaitcev","email":"775c8ea1f82a8ffb8cf58861cc6286708292a786@redhat.com"},"message":"usb: mon: Fix a deadlock in usbmon between mmap and read\n\nThe problem arises because our read() function grabs a lock of the\ncircular buffer, finds something of interest, then invokes copy_to_user()\nstraight from the buffer, which in turn takes mm->mmap_sem. In the same\ntime, the callback mon_bin_vma_fault() is invoked under mm->mmap_sem.\nIt attempts to take the fetch lock and deadlocks.\n\nThis patch does away with protecting of our page list with any\nsemaphores, and instead relies on the kernel not close the device\nwhile mmap is active in a process.\n\nIn addition, we prohibit re-sizing of a buffer while mmap is active.\nThis way, when (now unlocked) fault is processed, it works with the\npage that is intended to be mapped-in, and not some other random page.\nNote that this may have an ABI impact, but hopefully no legitimate\nprogram is this wrong.\n\nSigned-off-by: Pete Zaitcev <zaitcev@redhat.com>\nReported-by: syzbot+56f9673bb4cdcbeb0e92@syzkaller.appspotmail.com\nReviewed-by: Alan Stern <stern@rowland.harvard.edu>\nFixes: 46eb14a6e158 (\"USB: fix usbmon BUG trigger\")\nCc: <stable@vger.kernel.org>\nLink: https://lore.kernel.org/r/20191204203941.3503452b@suzdal.zaitcev.lan\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/19e6317d24c25ee737c65d1ffb7483bdda4bb54a"},{"sha":"392a9f63058f2cdcec8363b849a25532ee40da9f","author":{"name":"Florian Fainelli","email":"59190c1867e3222b932a0de3c668eb2d980d69a2@gmail.com"},"message":"dt-bindings: reset: Fix brcmstb-reset example\n\nThe reset controller has a #reset-cells value of 1, so we should see a\nphandle plus a register identifier, fix the example.\n\nFixes: 0807caf647dd (\"dt-bindings: reset: Add document for Broadcom STB reset controller\")\nSigned-off-by: Florian Fainelli <f.fainelli@gmail.com>\nSigned-off-by: Philipp Zabel <p.zabel@pengutronix.de>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/392a9f63058f2cdcec8363b849a25532ee40da9f"},{"sha":"ce89d8d3a70fa530e16f0b0f8994385a214cd0c0","author":{"name":"Florian Fainelli","email":"59190c1867e3222b932a0de3c668eb2d980d69a2@gmail.com"},"message":"reset: brcmstb: Remove resource checks\n\nThe use of IS_ALIGNED() is incorrect, the typical resource we pass looks\nlike this: start: 0x8404318, size: 0x30. When using IS_ALIGNED() we will\nget the following 0x8404318 & (0x18 - 1) = 0x10 which is definitively\nnot equal to 0, same goes with the size. These two checks would make the\ndriver fail probing.\n\nRemove the resource checks, since there should be no constraint on the\nbase addresse or size.\n\nFixes: 77750bc089e4 (\"reset: Add Broadcom STB SW_INIT reset controller driver\")\nSigned-off-by: Florian Fainelli <f.fainelli@gmail.com>\nSigned-off-by: Philipp Zabel <p.zabel@pengutronix.de>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/ce89d8d3a70fa530e16f0b0f8994385a214cd0c0"},{"sha":"723c0011c7f6992f57e2c629fa9c89141acc115f","author":{"name":"Geert Uytterhoeven","email":"a1ff81395f7e6bf5b509fe9aab06bf3419493e1d@glider.be"},"message":"reset: Fix {of,devm}_reset_control_array_get kerneldoc return types\n\nof_reset_control_array_get() and devm_reset_control_array_get() return\nstruct reset_control pointers, not internal struct reset_control_array\npointers, just like all other reset control API calls.\n\nCorrect the kerneldoc to match the code.\n\nFixes: 17c82e206d2a3cd8 (\"reset: Add APIs to manage array of resets\")\nSigned-off-by: Geert Uytterhoeven <geert+renesas@glider.be>\nSigned-off-by: Philipp Zabel <p.zabel@pengutronix.de>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/723c0011c7f6992f57e2c629fa9c89141acc115f"},{"sha":"db23808615e29d9a04f96806cac56f78b0fee0ef","author":{"name":"Geert Uytterhoeven","email":"a1ff81395f7e6bf5b509fe9aab06bf3419493e1d@glider.be"},"message":"reset: Do not register resource data for missing resets\n\nWhen an optional reset is not present, __devm_reset_control_get() and\ndevm_reset_control_array_get() still register resource data to release\nthe non-existing reset on cleanup, which is futile.\n\nFix this by skipping NULL reset control pointers.\n\nSigned-off-by: Geert Uytterhoeven <geert+renesas@glider.be>\nSigned-off-by: Philipp Zabel <p.zabel@pengutronix.de>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/db23808615e29d9a04f96806cac56f78b0fee0ef"},{"sha":"a470552ee8965da0fe6fd4df0aa39c4cda652c7c","author":{"name":"Ard Biesheuvel","email":"794a6ced5048c3c5bb2c726cbfcf957d00217421@kernel.org"},"message":"efi: Don't attempt to map RCI2 config table if it doesn't exist\n\nCommit:\n\n  1c5fecb61255aa12 (\"efi: Export Runtime Configuration Interface table to sysfs\")\n\n... added support for a Dell specific UEFI configuration table, but\nfailed to take into account that mapping the table should not be\nattempted unless the table actually exists. If it doesn't exist,\nthe code usually fails silently unless pr_debug() prints are\nenabled. However, on 32-bit PAE x86, the splat below is produced due\nto the attempt to map the placeholder value EFI_INVALID_TABLE_ADDR\nwhich we use for non-existing UEFI configuration tables, and which\nequals ULONG_MAX.\n\n   memremap attempted on mixed range 0x00000000ffffffff size: 0x1e\n   WARNING: CPU: 1 PID: 1 at kernel/iomem.c:81 memremap+0x1a3/0x1c0\n   Modules linked in:\n   CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.4.2-smp-mine #1\n   Hardware name: Hewlett-Packard HP Z400 Workstation/0B4Ch, BIOS 786G3 v03.61 03/05/2018\n   EIP: memremap+0x1a3/0x1c0\n  ...\n   Call Trace:\n    ? map_properties+0x473/0x473\n    ? efi_rci2_sysfs_init+0x2c/0x154\n    ? map_properties+0x473/0x473\n    ? do_one_initcall+0x49/0x1d4\n    ? parse_args+0x1e8/0x2a0\n    ? do_early_param+0x7a/0x7a\n    ? kernel_init_freeable+0x139/0x1c2\n    ? rest_init+0x8e/0x8e\n    ? kernel_init+0xd/0xf2\n    ? ret_from_fork+0x2e/0x38\n\nFix this by checking whether the table exists before attempting to map it.\n\nReported-by: Richard Narron <comet.berkeley@gmail.com>\nTested-by: Richard Narron <comet.berkeley@gmail.com>\nSigned-off-by: Ard Biesheuvel <ardb@kernel.org>\nCc: linux-efi@vger.kernel.org\nFixes: 1c5fecb61255aa12 (\"efi: Export Runtime Configuration Interface table to sysfs\")\nLink: https://lkml.kernel.org/r/20191210090945.11501-2-ardb@kernel.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/a470552ee8965da0fe6fd4df0aa39c4cda652c7c"},{"sha":"37a68eab4cd92b507c9e8afd760fdc18e4fecac6","author":{"name":"Hans de Goede","email":"9fa1be1a5b5729e4c6b404f34c9ce49ff4882fd8@redhat.com"},"message":"drm/nouveau: Move the declaration of struct nouveau_conn_atom up a bit\n\nPlace the declaration of struct nouveau_conn_atom above that of\nstruct nouveau_connector. This commit makes no changes to the moved\nblock what so ever, it just moves it up a bit.\n\nThis is a preparation patch to fix some issues with connector handling\non pre nv50 displays (which do not use atomic modesetting).\n\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nReviewed-by: Lyude Paul <lyude@redhat.com>\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/37a68eab4cd92b507c9e8afd760fdc18e4fecac6"},{"sha":"64d17f25dcad518461ccf0c260544e1e379c5b35","author":{"name":"Hans de Goede","email":"9fa1be1a5b5729e4c6b404f34c9ce49ff4882fd8@redhat.com"},"message":"drm/nouveau: Fix drm-core using atomic code-paths on pre-nv50 hardware\n\nWe do not support atomic modesetting on pre-nv50 hardware, but until now\nour connector code was setting drm_connector->state on pre-nv50 hardware.\n\nThis causes the core to enter atomic modesetting paths in at least:\n\n1. drm_connector_get_encoder(), returning connector->state->best_encoder\nwhich is always 0, causing us to always report 0 as encoder_id in\nthe drmModeConnector struct returned by drmModeGetConnector().\n\n2. drm_encoder_get_crtc(), returning NULL because uses_atomic get set,\ncausing us to always report 0 as crtc_id in the drmModeEncoder struct\nreturned by drmModeGetEncoder()\n\nWhich in turn confuses userspace, at least plymouth thinks that the pipe\nhas changed because of this and tries to reconfigure it unnecessarily.\n\nMore in general we should not set drm_connector->state in the non-atomic\ncode as this violates the drm-core's expectations.\n\nThis commit fixes this by using a nouveau_conn_atom struct embedded in the\nnouveau_connector struct for property handling in the non-atomic case.\n\nFixes: https://bugzilla.redhat.com/show_bug.cgi?id=1706557\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/64d17f25dcad518461ccf0c260544e1e379c5b35"},{"sha":"310d35771ee9040f5744109fc277206ad96ba253","author":{"name":"Lyude Paul","email":"1d05c5face2dc786c0af2cf362656a51f0df9b63@redhat.com"},"message":"drm/nouveau/kms/nv50-: Call outp_atomic_check_view() before handling PBN\n\nSince nv50_outp_atomic_check_view() can set crtc_state->mode_changed, we\nprobably should be calling it before handling any PBN changes. Just a\nprecaution.\n\nSigned-off-by: Lyude Paul <lyude@redhat.com>\nFixes: 232c9eec417a (\"drm/nouveau: Use atomic VCPI helpers for MST\")\nCc: Ben Skeggs <bskeggs@redhat.com>\nCc: Daniel Vetter <daniel.vetter@ffwll.ch>\nCc: David Airlie <airlied@redhat.com>\nCc: Jerry Zuo <Jerry.Zuo@amd.com>\nCc: Harry Wentland <harry.wentland@amd.com>\nCc: Juston Li <juston.li@intel.com>\nCc: Sean Paul <seanpaul@chromium.org>\nCc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nCc: <stable@vger.kernel.org> # v5.1+\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/310d35771ee9040f5744109fc277206ad96ba253"},{"sha":"ac2d9275f371346922b31a388bbaa6a54f1154a4","author":{"name":"Lyude Paul","email":"1d05c5face2dc786c0af2cf362656a51f0df9b63@redhat.com"},"message":"drm/nouveau/kms/nv50-: Store the bpc we're using in nv50_head_atom\n\nIn order to be able to use bpc values that are different from what the\nconnector reports, we want to be able to store the bpc value we decide\non using for an atomic state in nv50_head_atom and refer to that instead\nof simply using the value that the connector reports throughout the\nwhole atomic check phase and commit phase. This will let us (eventually)\nimplement the max bpc connector property, and will also be needed for\nlimiting the bpc we use on MST displays to 8 in the next commit.\n\nSigned-off-by: Lyude Paul <lyude@redhat.com>\nFixes: 232c9eec417a (\"drm/nouveau: Use atomic VCPI helpers for MST\")\nCc: Ben Skeggs <bskeggs@redhat.com>\nCc: Daniel Vetter <daniel.vetter@ffwll.ch>\nCc: David Airlie <airlied@redhat.com>\nCc: Jerry Zuo <Jerry.Zuo@amd.com>\nCc: Harry Wentland <harry.wentland@amd.com>\nCc: Juston Li <juston.li@intel.com>\nCc: Sean Paul <seanpaul@chromium.org>\nCc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nCc: <stable@vger.kernel.org> # v5.1+\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/ac2d9275f371346922b31a388bbaa6a54f1154a4"},{"sha":"ae5769d4670982bc483885b120b557a9ffd57527","author":{"name":"Lyude Paul","email":"1d05c5face2dc786c0af2cf362656a51f0df9b63@redhat.com"},"message":"drm/nouveau/kms/nv50-: Limit MST BPC to 8\n\nNoticed this while working on some unrelated CRC stuff. Currently,\nuserspace has very little support for BPCs higher than 8. While this\ndoesn't matter for most things, on MST topologies we need to be careful\nabout ensuring that we do our best to make any given display\nconfiguration fit within the bandwidth restraints of the topology, since\notherwise less people's monitor configurations will work.\n\nAllowing for BPC settings higher than 8 dramatically increases the\nrequired bandwidth for displays in most configurations, and consequently\nmakes it a lot less likely that said display configurations will pass\nthe atomic check.\n\nIn the future we want to fix this correctly by making it so that we\nadjust the bpp for each display in a topology to be as high as possible,\nwhile making sure to lower the bpp of each display in the event that we\nrun out of bandwidth and need to rerun our atomic check. But for now,\nfollow the behavior that both i915 and amdgpu are sticking to.\n\nSigned-off-by: Lyude Paul <lyude@redhat.com>\nFixes: 232c9eec417a (\"drm/nouveau: Use atomic VCPI helpers for MST\")\nCc: Ben Skeggs <bskeggs@redhat.com>\nCc: Daniel Vetter <daniel.vetter@ffwll.ch>\nCc: David Airlie <airlied@redhat.com>\nCc: Jerry Zuo <Jerry.Zuo@amd.com>\nCc: Harry Wentland <harry.wentland@amd.com>\nCc: Juston Li <juston.li@intel.com>\nCc: Sam Ravnborg <sam@ravnborg.org>\nCc: Sean Paul <seanpaul@chromium.org>\nCc: <stable@vger.kernel.org> # v5.1+\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/ae5769d4670982bc483885b120b557a9ffd57527"},{"sha":"3d1890ef8023e61934e070021b06cc9f417260c0","author":{"name":"Ben Skeggs","email":"d9f27fb07c1e9f131223ad827fa5179f3846c30b@redhat.com"},"message":"drm/nouveau/kms/nv50-: fix panel scaling\n\nUnder certain circumstances, encoder atomic_check() can be entered\nwithout adjusted_mode having been reset to the same as mode, which\nconfuses the scaling logic and can lead to a misprogrammed display.\n\nFix this by checking against the user-provided mode directly.\n\nLink: https://bugs.freedesktop.org/show_bug.cgi?id=108615\nLink: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/464\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/3d1890ef8023e61934e070021b06cc9f417260c0"},{"sha":"7c5a2df3367a2c4984f1300261345817d95b71f8","author":{"name":"Johan Hovold","email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org"},"message":"USB: serial: io_edgeport: fix epic endpoint lookup\n\nMake sure to use the current alternate setting when looking up the\nendpoints on epic devices to avoid binding to an invalid interface.\n\nFailing to do so could cause the driver to misbehave or trigger a WARN()\nin usb_submit_urb() that kernels with panic_on_warn set would choke on.\n\nFixes: 6e8cf7751f9f (\"USB: add EPIC support to the io_edgeport driver\")\nCc: stable <stable@vger.kernel.org>     # 2.6.21\nSigned-off-by: Johan Hovold <johan@kernel.org>\nLink: https://lore.kernel.org/r/20191210112601.3561-5-johan@kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/7c5a2df3367a2c4984f1300261345817d95b71f8"},{"sha":"59920635b89d74b9207ea803d5e91498d39e8b69","author":{"name":"Johan Hovold","email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org"},"message":"USB: idmouse: fix interface sanity checks\n\nMake sure to use the current alternate setting when verifying the\ninterface descriptors to avoid binding to an invalid interface.\n\nFailing to do so could cause the driver to misbehave or trigger a WARN()\nin usb_submit_urb() that kernels with panic_on_warn set would choke on.\n\nFixes: 1da177e4c3f4 (\"Linux-2.6.12-rc2\")\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nLink: https://lore.kernel.org/r/20191210112601.3561-4-johan@kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/59920635b89d74b9207ea803d5e91498d39e8b69"},{"sha":"3c11c4bed02b202e278c0f5c319ae435d7fb9815","author":{"name":"Johan Hovold","email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org"},"message":"USB: adutux: fix interface sanity check\n\nMake sure to use the current alternate setting when verifying the\ninterface descriptors to avoid binding to an invalid interface.\n\nFailing to do so could cause the driver to misbehave or trigger a WARN()\nin usb_submit_urb() that kernels with panic_on_warn set would choke on.\n\nFixes: 03270634e242 (\"USB: Add ADU support for Ontrak ADU devices\")\nCc: stable <stable@vger.kernel.org>     # 2.6.19\nSigned-off-by: Johan Hovold <johan@kernel.org>\nLink: https://lore.kernel.org/r/20191210112601.3561-3-johan@kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/3c11c4bed02b202e278c0f5c319ae435d7fb9815"},{"sha":"09068c1ad53fb077bdac288869dec2435420bdc4","author":{"name":"Johan Hovold","email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org"},"message":"USB: atm: ueagle-atm: add missing endpoint check\n\nMake sure that the interrupt interface has an endpoint before trying to\naccess its endpoint descriptors to avoid dereferencing a NULL pointer.\n\nThe driver binds to the interrupt interface with interface number 0, but\nmust not assume that this interface or its current alternate setting are\nthe first entries in the corresponding configuration arrays.\n\nFixes: b72458a80c75 (\"[PATCH] USB: Eagle and ADI 930 usb adsl modem driver\")\nCc: stable <stable@vger.kernel.org>     # 2.6.16\nSigned-off-by: Johan Hovold <johan@kernel.org>\nLink: https://lore.kernel.org/r/20191210112601.3561-2-johan@kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/09068c1ad53fb077bdac288869dec2435420bdc4"},{"sha":"74ca34118a0e05793935d804ccffcedd6eb56596","author":{"name":"Johan Hovold","email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org"},"message":"staging: rtl8188eu: fix interface sanity check\n\nMake sure to use the current alternate setting when verifying the\ninterface descriptors to avoid binding to an invalid interface.\n\nFailing to do so could cause the driver to misbehave or trigger a WARN()\nin usb_submit_urb() that kernels with panic_on_warn set would choke on.\n\nFixes: c2478d39076b (\"staging: r8188eu: Add files for new driver - part 20\")\nCc: stable <stable@vger.kernel.org>     # 3.12\nSigned-off-by: Johan Hovold <johan@kernel.org>\nLink: https://lore.kernel.org/r/20191210114751.5119-2-johan@kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/74ca34118a0e05793935d804ccffcedd6eb56596"},{"sha":"c724f776f048538ecfdf53a52b7a522309f5c504","author":{"name":"Johan Hovold","email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org"},"message":"staging: rtl8712: fix interface sanity check\n\nMake sure to use the current alternate setting when verifying the\ninterface descriptors to avoid binding to an invalid interface.\n\nFailing to do so could cause the driver to misbehave or trigger a WARN()\nin usb_submit_urb() that kernels with panic_on_warn set would choke on.\n\nFixes: 2865d42c78a9 (\"staging: r8712u: Add the new driver to the mainline kernel\")\nCc: stable <stable@vger.kernel.org>     # 2.6.37\nSigned-off-by: Johan Hovold <johan@kernel.org>\nLink: https://lore.kernel.org/r/20191210114751.5119-3-johan@kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/c724f776f048538ecfdf53a52b7a522309f5c504"},{"sha":"8c7d4b7b3d43c54c0b8c1e4adb917a151c754196","author":{"name":"Tejas Joglekar","email":"f9c1eb7d25b74e8ae777b7c4b379c2fe777b1305@synopsys.com"},"message":"usb: dwc3: gadget: Fix logical condition\n\nThis patch corrects the condition to kick the transfer without\ngiving back the requests when either request has remaining data\nor when there are pending SGs. The && check was introduced during\nspliting up the dwc3_gadget_ep_cleanup_completed_requests() function.\n\nFixes: f38e35dd84e2 (\"usb: dwc3: gadget: split dwc3_gadget_ep_cleanup_completed_requests()\")\n\nCc: stable@vger.kernel.org\nSigned-off-by: Tejas Joglekar <joglekar@synopsys.com>\nSigned-off-by: Felipe Balbi <balbi@kernel.org>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/8c7d4b7b3d43c54c0b8c1e4adb917a151c754196"},{"sha":"d3abda5a98a18e524e17fd4085c9f4bd53e9ef53","author":{"name":"Thinh Nguyen","email":"8e436f42a8d87f445466a3edb7bd598ad284eedd@synopsys.com"},"message":"usb: dwc3: gadget: Clear started flag for non-IOC\n\nNormally the END_TRANSFER command completion handler will clear the\nDWC3_EP_TRANSFER_STARTED flag. However, if the command was sent without\ninterrupt on completion, then the flag will not be cleared. Make sure to\nclear the flag in this case.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Thinh Nguyen <thinhn@synopsys.com>\nSigned-off-by: Felipe Balbi <balbi@kernel.org>","distinct":false,"url":"https://api.github.com/repos/metux/linux/commits/d3abda5a98a18e524e17fd4085c9f4bd53e9ef53"}]}
{"actor":{"display_login":"metux"}}