{"push_id":1289245125,"size":66,"distinct_size":66,"ref":"refs/heads/linux-4.1.y","head":"3b60b86aec06fbae1142ccc4e55b39b529ae2a25","before":"99f614a3bb23603a947be2e95b78507112c484e5","commits":[{"sha":"beebc82b1cf1710ffebebdff4e09b3455085fa94","author":{"name":"Andrew Donnellan","email":"88f9fbfa5a7fc0c41e284752e169a16d1d6535b0@au1.ibm.com"},"message":"powerpc/eeh: eeh_pci_enable(): fix checking of post-request state\n\n[ Upstream commit 949e9b827eb4736d96df520c67d07a54c64e99b8 ]\n\nIn eeh_pci_enable(), after making the request to set the new options, we\ncall eeh_ops->wait_state() to check that the request finished successfully.\n\nAt the moment, if eeh_ops->wait_state() returns 0, we return 0 without\nchecking that it reflects the expected outcome. This can lead to callers\nfurther up the chain incorrectly assuming the slot has been successfully\nunfrozen and continuing to attempt recovery.\n\nOn powernv, this will occur if pnv_eeh_get_pe_state() or\npnv_eeh_get_phb_state() return 0, which in turn occurs if the relevant OPAL\ncall returns OPAL_EEH_STOPPED_MMIO_DMA_FREEZE or\nOPAL_EEH_PHB_ERROR respectively.\n\nOn pseries, this will occur if pseries_eeh_get_state() returns 0, which in\nturn occurs if RTAS reports that the PE is in the MMIO Stopped and DMA\nStopped states.\n\nObviously, none of these cases represent a successful completion of a\nrequest to thaw MMIO or DMA.\n\nFix the check so that a wait_state() return value of 0 won't be considered\nsuccessful for the EEH_OPT_THAW_MMIO or EEH_OPT_THAW_DMA cases.\n\nSigned-off-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>\nAcked-by: Gavin Shan <gwshan@linux.vnet.ibm.com>\nReviewed-by: Daniel Axtens <dja@axtens.net>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/beebc82b1cf1710ffebebdff4e09b3455085fa94"},{"sha":"2b211174edd454376ab9bc85f7bae8e01016d87c","author":{"name":"Eric Dumazet","email":"b3d77ad2db30f558882cc0c038be5a3cf96611f9@google.com"},"message":"tcp: make challenge acks less predictable\n\n[ Upstream commit 75ff39ccc1bd5d3c455b6822ab09e533c551f758 ]\n\nYue Cao claims that current host rate limiting of challenge ACKS\n(RFC 5961) could leak enough information to allow a patient attacker\nto hijack TCP sessions. He will soon provide details in an academic\npaper.\n\nThis patch increases the default limit from 100 to 1000, and adds\nsome randomization so that the attacker can no longer hijack\nsessions without spending a considerable amount of probes.\n\nBased on initial analysis and patch from Linus.\n\nNote that we also have per socket rate limiting, so it is tempting\nto remove the host limit in the future.\n\nv2: randomize the count of challenge acks per second, not the period.\n\nFixes: 282f23c6ee34 (\"tcp: implement RFC 5961 3.2\")\nReported-by: Yue Cao <ycao009@ucr.edu>\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nSuggested-by: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Yuchung Cheng <ycheng@google.com>\nCc: Neal Cardwell <ncardwell@google.com>\nAcked-by: Neal Cardwell <ncardwell@google.com>\nAcked-by: Yuchung Cheng <ycheng@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/2b211174edd454376ab9bc85f7bae8e01016d87c"},{"sha":"2dd916fce77144aaa8fb554a2b41be73635ee650","author":{"name":"Jason Baron","email":"623d78bc3405eaae037ff64ede55814f5ac5c013@akamai.com"},"message":"tcp: enable per-socket rate limiting of all 'challenge acks'\n\n[ Upstream commit 083ae308280d13d187512b9babe3454342a7987e ]\n\nThe per-socket rate limit for 'challenge acks' was introduced in the\ncontext of limiting ack loops:\n\ncommit f2b2c582e824 (\"tcp: mitigate ACK loops for connections as tcp_sock\")\n\nAnd I think it can be extended to rate limit all 'challenge acks' on a\nper-socket basis.\n\nSince we have the global tcp_challenge_ack_limit, this patch allows for\ntcp_challenge_ack_limit to be set to a large value and effectively rely on\nthe per-socket limit, or set tcp_challenge_ack_limit to a lower value and\nstill prevents a single connections from consuming the entire challenge ack\nquota.\n\nIt further moves in the direction of eliminating the global limit at some\npoint, as Eric Dumazet has suggested. This a follow-up to:\nSubject: tcp: make challenge acks less predictable\n\nCc: Eric Dumazet <edumazet@google.com>\nCc: David S. Miller <davem@davemloft.net>\nCc: Neal Cardwell <ncardwell@google.com>\nCc: Yuchung Cheng <ycheng@google.com>\nCc: Yue Cao <ycao009@ucr.edu>\nSigned-off-by: Jason Baron <jbaron@akamai.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/2dd916fce77144aaa8fb554a2b41be73635ee650"},{"sha":"4bb0ddaf9330fd4c1359cd98cb9aa2f3131d769c","author":{"name":"Felix Fietkau","email":"8cf1b58efcecbc12846b1b7b0c62f2bc67216d26@nbd.name"},"message":"mac80211: fix purging multicast PS buffer queue\n\n[ Upstream commit 6b07d9ca9b5363dda959b9582a3fc9c0b89ef3b5 ]\n\nThe code currently assumes that buffered multicast PS frames don't have\na pending ACK frame for tx status reporting.\nHowever, hostapd sends a broadcast deauth frame on teardown for which tx\nstatus is requested. This can lead to the \"Have pending ack frames\"\nwarning on module reload.\nFix this by using ieee80211_free_txskb/ieee80211_purge_tx_queue.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Felix Fietkau <nbd@nbd.name>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/4bb0ddaf9330fd4c1359cd98cb9aa2f3131d769c"},{"sha":"cbae57635b20802b211e281a7dc7fcf56316e36e","author":{"name":"Lubomir Rintel","email":"5fd9c3d43dc3364702889daff5ebadc6fc8bb13b@v3.sk"},"message":"USB: serial: option: add D-Link DWM-156/A3\n\n[ Upstream commit cf1b18030de29e4e5b0a57695ae5db4a89da0ff7 ]\n\nThe device has four interfaces; the three serial ports ought to be\nhandled by this driver:\n\n00 Diagnostic interface serial port\n01 NMEA device serial port\n02 Mass storage (sd card)\n03 Modem serial port\n\nThe other product ids listed in the Windows driver are present already.\n\nSigned-off-by: Lubomir Rintel <lkundrak@v3.sk>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/cbae57635b20802b211e281a7dc7fcf56316e36e"},{"sha":"65b2f0af0dfc3be7ac1f1302db7bf64184b3a821","author":{"name":"Robert Deliën","email":"b93e48b8445e5b838ee3472c32911ea601bd3bb0@delien.nl"},"message":"USB: serial: ftdi_sio: add PIDs for Ivium Technologies devices\n\n[ Upstream commit 6977495c06f7f47636a076ee5a0ca571279d9697 ]\n\nIvium Technologies uses the FTDI VID with custom PIDs for their line of\nelectrochemical interfaces and the PalmSens they developed for PalmSens\nBV.\n\nSigned-off-by: Robert Delien <robert@delien.nl>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/65b2f0af0dfc3be7ac1f1302db7bf64184b3a821"},{"sha":"2980f143e9f9caaf53808f2106fbafc6151646ec","author":{"name":"Sheng-Hui J. Chu","email":"4ea9e3f8e82030155772554a42f02a9e4bc9e1d1@gmail.com"},"message":"USB: serial: ftdi_sio: add device ID for WICED USB UART dev board\n\n[ Upstream commit ae34d12cc1e212ffcd92e069030e54dae69c832f ]\n\nBCM20706V2_EVAL is a WICED dev board designed with FT2232H USB 2.0\nUART/FIFO IC.\n\nTo support BCM920706V2_EVAL dev board for WICED development on Linux.\nAdd the VID(0a5c) and PID(6422) to ftdi_sio driver to allow loading\nftdi_sio for this board.\n\nSigned-off-by: Sheng-Hui J. Chu <s.jeffrey.chu@gmail.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/2980f143e9f9caaf53808f2106fbafc6151646ec"},{"sha":"61882ca3c2050d4821738454cb4966dcf8097fc5","author":{"name":"Daniele Palmas","email":"8eadd4e0f410715cd0bee604d0bbc31740484d9b@gmail.com"},"message":"USB: serial: option: add support for Telit LE920A4\n\n[ Upstream commit 01d7956b58e644ea0d2e8d9340c5727a8fc39d70 ]\n\nThis patch adds a set of compositions for Telit LE920A4.\n\nCompositions in short are:\n\n0x1207: tty + tty\n0x1208: tty + adb + tty + tty\n0x1211: tty + adb + ecm\n0x1212: tty + adb\n0x1213: ecm + tty\n0x1214: tty + adb + ecm + tty\n\ntelit_le922_blacklist_usbcfg3 is reused for compositions 0x1211\nand 0x1214 due to the same interfaces positions.\n\nSigned-off-by: Daniele Palmas <dnlplm@gmail.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/61882ca3c2050d4821738454cb4966dcf8097fc5"},{"sha":"6a19c730de76c8b870a72035416a45ea47cb8e75","author":{"name":"Alexey Klimov","email":"e28dfbf0a6996bf3673b668640f9e20275eae331@gmail.com"},"message":"USB: serial: fix memleak in driver-registration error path\n\n[ Upstream commit 647024a7df36014bbc4479d92d88e6b77c0afcf6 ]\n\nudriver struct allocated by kzalloc() will not be freed\nif usb_register() and next calls fail. This patch fixes this\nby adding one more step with kfree(udriver) in error path.\n\nSigned-off-by: Alexey Klimov <klimov.linux@gmail.com>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/6a19c730de76c8b870a72035416a45ea47cb8e75"},{"sha":"e989e0c9bba5c1f8987629e2880a512d7b15e852","author":{"name":"Dave Carroll","email":"b29f82b30544672af64ad35fbbcd8c458c682cf4@microsemi.com"},"message":"aacraid: Check size values after double-fetch from user\n\n[ Upstream commit fa00c437eef8dc2e7b25f8cd868cfa405fcc2bb3 ]\n\nIn aacraid's ioctl_send_fib() we do two fetches from userspace, one the\nget the fib header's size and one for the fib itself. Later we use the\nsize field from the second fetch to further process the fib. If for some\nreason the size from the second fetch is different than from the first\nfix, we may encounter an out-of- bounds access in aac_fib_send(). We\nalso check the sender size to insure it is not out of bounds. This was\nreported in https://bugzilla.kernel.org/show_bug.cgi?id=116751 and was\nassigned CVE-2016-6480.\n\nReported-by: Pengfei Wang <wpengfeinudt@gmail.com>\nFixes: 7c00ffa31 '[SCSI] 2.6 aacraid: Variable FIB size (updated patch)'\nCc: stable@vger.kernel.org\nSigned-off-by: Dave Carroll <david.carroll@microsemi.com>\nReviewed-by: Johannes Thumshirn <jthumshirn@suse.de>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/e989e0c9bba5c1f8987629e2880a512d7b15e852"},{"sha":"aca78034833166c848505b391b258ecbb96c895b","author":{"name":"Russell King","email":"8640768d851c67eb4c0e8bfcf2aabcc8010b9372@armlinux.org.uk"},"message":"crypto: caam - fix non-hmac hashes\n\n[ Upstream commit a0118c8b2be9297aed8e915c60b4013326b256d4 ]\n\nSince 6de62f15b581 (\"crypto: algif_hash - Require setkey before\naccept(2)\"), the AF_ALG interface requires userspace to provide a key\nto any algorithm that has a setkey method.  However, the non-HMAC\nalgorithms are not keyed, so setting a key is unnecessary.\n\nFix this by removing the setkey method from the non-keyed hash\nalgorithms.\n\nFixes: 6de62f15b581 (\"crypto: algif_hash - Require setkey before accept(2)\")\nCc: <stable@vger.kernel.org>\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/aca78034833166c848505b391b258ecbb96c895b"},{"sha":"fdcdf5bac083b93871d4762feeae99caf85bf325","author":{"name":"Viresh Kumar","email":"4ca49bc1dcfdfc376d29da1eb07a3e0b3cd46daa@linaro.org"},"message":"usb: hub: Fix unbalanced reference count/memory leak/deadlocks\n\n[ Upstream commit 6bb47e8ab98accb1319bd43c64966340ba3bba9a ]\n\nMemory leak and unbalanced reference count:\n\nIf the hub gets disconnected while the core is still activating it, this\ncan result in leaking memory of few USB structures.\n\nThis will happen if we have done a kref_get() from hub_activate() and\nscheduled a delayed work item for HUB_INIT2/3. Now if hub_disconnect()\ngets called before the delayed work expires, then we will cancel the\nwork from hub_quiesce(), but wouldn't do a kref_put(). And so the\nunbalance.\n\nkmemleak reports this as (with the commit e50293ef9775 backported to\n3.10 kernel with other changes, though the same is true for mainline as\nwell):\n\nunreferenced object 0xffffffc08af5b800 (size 1024):\n  comm \"khubd\", pid 73, jiffies 4295051211 (age 6482.350s)\n  hex dump (first 32 bytes):\n    30 68 f3 8c c0 ff ff ff 00 a0 b2 2e c0 ff ff ff  0h..............\n    01 00 00 00 00 00 00 00 00 94 7d 40 c0 ff ff ff  ..........}@....\n  backtrace:\n    [<ffffffc0003079ec>] create_object+0x148/0x2a0\n    [<ffffffc000cc150c>] kmemleak_alloc+0x80/0xbc\n    [<ffffffc000303a7c>] kmem_cache_alloc_trace+0x120/0x1ac\n    [<ffffffc0006fa610>] hub_probe+0x120/0xb84\n    [<ffffffc000702b20>] usb_probe_interface+0x1ec/0x298\n    [<ffffffc0005d50cc>] driver_probe_device+0x160/0x374\n    [<ffffffc0005d5308>] __device_attach+0x28/0x4c\n    [<ffffffc0005d3164>] bus_for_each_drv+0x78/0xac\n    [<ffffffc0005d4ee0>] device_attach+0x6c/0x9c\n    [<ffffffc0005d42b8>] bus_probe_device+0x28/0xa0\n    [<ffffffc0005d23a4>] device_add+0x324/0x604\n    [<ffffffc000700fcc>] usb_set_configuration+0x660/0x6cc\n    [<ffffffc00070a350>] generic_probe+0x44/0x84\n    [<ffffffc000702914>] usb_probe_device+0x54/0x74\n    [<ffffffc0005d50cc>] driver_probe_device+0x160/0x374\n    [<ffffffc0005d5308>] __device_attach+0x28/0x4c\n\nDeadlocks:\n\nIf the hub gets disconnected early enough (i.e. before INIT2/INIT3 are\nfinished and the init_work is still queued), the core may call\nhub_quiesce() after acquiring interface device locks and it will wait\nfor the work to be cancelled synchronously. But if the work handler is\nalready running in parallel, it may try to acquire the same interface\ndevice lock and this may result in deadlock.\n\nFix both the issues by removing the call to cancel_delayed_work_sync().\n\nCC: <stable@vger.kernel.org> #4.4+\nFixes: e50293ef9775 (\"USB: fix invalid memory access in hub_activate()\")\nReported-by: Manu Gautam <mgautam@codeaurora.org>\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/fdcdf5bac083b93871d4762feeae99caf85bf325"},{"sha":"5bd6b61399ab2a4c024389fd64c02b099c8fff95","author":{"name":"Marc Ohlf","email":"ad71ae69c0b1fbac8d38c2aa2ee892d3a402ff26@mkt-sys.de"},"message":"usb: ehci: change order of register cleanup during shutdown\n\n[ Upstream commit bc337b51508beb2d039aff5074a76cfe1c212030 ]\n\nIn ehci_turn_off_all_ports() all EHCI port registers are cleared to zero.\nOn some hardware, this can lead to an system hang,\nwhen ehci_port_power() accesses the already cleared registers.\n\nThis patch changes the order of cleanup.\nFirst call ehci_port_power() which respects the current bits in\nport status registers\nand afterwards cleanup the hard way by setting everything to zero.\n\nSigned-off-by: Marc Ohlf <ohlf@mkt-sys.de>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nCC: <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/5bd6b61399ab2a4c024389fd64c02b099c8fff95"},{"sha":"d3c1edbd4f11a838785af3c48a1885f6b94935ad","author":{"name":"Stefan Haberland","email":"c25de1589b4a1a2d9eb6398122abafeef7ef78a2@linux.vnet.ibm.com"},"message":"s390/dasd: fix hanging device after clear subchannel\n\n[ Upstream commit 9ba333dc55cbb9523553df973adb3024d223e905 ]\n\nWhen a device is in a status where CIO has killed all I/O by itself the\ninterrupt for a clear request may not contain an irb to determine the\nclear function. Instead it contains an error pointer -EIO.\nThis was ignored by the DASD int_handler leading to a hanging device\nwaiting for a clear interrupt.\n\nHandle -EIO error pointer correctly for requests that are clear pending and\ntreat the clear as successful.\n\nSigned-off-by: Stefan Haberland <sth@linux.vnet.ibm.com>\nReviewed-by: Sebastian Ott <sebott@linux.vnet.ibm.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/d3c1edbd4f11a838785af3c48a1885f6b94935ad"},{"sha":"60b8bcfd6a911071c8eb7de6bb9c1afc964385f1","author":{"name":"Felipe Balbi","email":"839ce88010ac82d4d5954e11ee7a7e49086a4b3e@linux.intel.com"},"message":"usb: dwc3: gadget: increment request->actual once\n\n[ Upstream commit c7de573471832dff7d31f0c13b0f143d6f017799 ]\n\nWhen using SG lists, we would end up setting\nrequest->actual to:\n\n\tnum_mapped_sgs * (request->length - count)\n\nLet's fix that up by incrementing request->actual\nonly once.\n\nCc: <stable@vger.kernel.org>\nReported-by: Brian E Rogers <brian.e.rogers@intel.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/60b8bcfd6a911071c8eb7de6bb9c1afc964385f1"},{"sha":"a694f3fa30adc8be36d7e2f8e4911a3fe705adf2","author":{"name":"Felipe Balbi","email":"839ce88010ac82d4d5954e11ee7a7e49086a4b3e@linux.intel.com"},"message":"usb: dwc3: gadget: fix for short pkts during chained xfers\n\n[ Upstream commit e5b36ae2f851024d43c76e51f395d32ce8d769ce ]\n\nDWC3 has one interesting peculiarity with chained\ntransfers. If we setup N chained transfers and we\nget a short packet before processing all N TRBs,\nDWC3 will (conditionally) issue a XferComplete or\nXferInProgress event and retire all TRBs from the\none which got a short packet to the last without\nclearing their HWO bits.\n\nThis means SW must clear HWO bit manually, which\nthis patch is doing.\n\nCc: <stable@vger.kernel.org>\nCc: Brian E Rogers <brian.e.rogers@intel.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/a694f3fa30adc8be36d7e2f8e4911a3fe705adf2"},{"sha":"b42468438321297c27cca67a20d09b22d0bc486f","author":{"name":"Felipe Balbi","email":"839ce88010ac82d4d5954e11ee7a7e49086a4b3e@linux.intel.com"},"message":"usb: dwc3: gadget: always cleanup all TRBs\n\n[ Upstream commit 7c705dfe2ebe731c8fd068623b6b4df2d3512c08 ]\n\nIf we stop earlier due to short packet, we will\nnot be able to giveback all TRBs.\n\nCc: <stable@vger.kernel.org>\nCc: Brian E Rogers <brian.e.rogers@intel.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/b42468438321297c27cca67a20d09b22d0bc486f"},{"sha":"888ea95a19eb3abde8373f68cd6fd8e65785570c","author":{"name":"John Youn","email":"a1a9a1aef1e39d59cf8ccc482b4cb59f6a51c39b@synopsys.com"},"message":"usb: dwc3: pci: trivial: Formatting\n\n[ Upstream commit 9a5a0783e4910d9e2063e87184fbd9cac7161a16 ]\n\nFix the alignment of the PCI device definitions. Also change the hex\ndigit capitalization of one constant to make it consistent with the\nrest of the file and driver.\n\nSigned-off-by: John Youn <johnyoun@synopsys.com>\nSigned-off-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/888ea95a19eb3abde8373f68cd6fd8e65785570c"},{"sha":"f034f1c6e8075ca3e294babd578ada5daef9d4c1","author":{"name":"Heikki Krogerus","email":"3c62c34689f9dfbaa6fbe874458f441fc5ace1cc@linux.intel.com"},"message":"usb: dwc3: pci: add support for Intel Broxton SOC\n\n[ Upstream commit b4c580a43d520b7812c0fd064fbab929ce2f1da0 ]\n\nPCI IDs for Broxton based platforms.\n\nSigned-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>\nSigned-off-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/f034f1c6e8075ca3e294babd578ada5daef9d4c1"},{"sha":"f079b0e5a9bba59b1befd390b81a1819dd41e19d","author":{"name":"Heikki Krogerus","email":"3c62c34689f9dfbaa6fbe874458f441fc5ace1cc@linux.intel.com"},"message":"usb: dwc3: pci: add Intel Kabylake PCI ID\n\n[ Upstream commit 4491ed5042f0419b22a4b08331adb54af31e2caa ]\n\nIntel Kabylake PCH has the same DWC3 than Intel\nSunrisepoint. Add the new ID to the supported devices.\n\nCc: <stable@vger.kernel.org>\nSigned-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/sunny256/linux/commits/f079b0e5a9bba59b1befd390b81a1819dd41e19d"}]}
{"actor":{"display_login":"sunny256"}}