{"push_id":922577066,"size":1000,"distinct_size":1472,"ref":"refs/heads/android-hikey-linaro-4.1","head":"4dc90021b8af8de9f2097c13d7a7e15470fc83d2","before":"ef2c679bc4130f0ef8672642e8402bcb01afe3a9","commits":[{"sha":"7a64ba1a070e33af42f21811886497ee33030670","author":{"email":"7351ee4254d3ae583dd8772c904897a231cf4948@gmail.com","name":"Peng Fan"},"message":"mmc: sdhci check parameters before call dma_free_coherent\n\ncommit 7ac020366b0a436d726408841160b5dc32c19214 upstream.\n\nWe should not call dma_free_coherent if host->adma_table is NULL,\notherwise may trigger panic.\n\nFixes: d1e49f77d7c7 (\"mmc: sdhci: convert ADMA descriptors to a...\")\nSigned-off-by: Peng Fan <van.freenix@gmail.com>\nAcked-by: Adrian Hunter <adrian.hunter@intel.com>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/7a64ba1a070e33af42f21811886497ee33030670"},{"sha":"a53ccf3cfe09ff026dd0d38a4211bf5766743ba3","author":{"email":"28ec1adb181e0f7ff73a9ed1532c061a187559fb@transmode.se","name":"Joakim Tjernlund"},"message":"mmc: sdhci-esdhc: Make 8BIT bus work\n\ncommit 8e91125ff3f57f15c6568e2a6d32743b3f7815e4 upstream.\n\nSupport for 8BIT bus with was added some time ago to sdhci-esdhc but\nthen missed to remove the 8BIT from the reserved bit mask which made\n8BIT non functional.\n\nFixes: 66b50a00992d (\"mmc: esdhc: Add support for 8-bit bus width and..\")\nSigned-off-by: Joakim Tjernlund <joakim.tjernlund@transmode.se>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/a53ccf3cfe09ff026dd0d38a4211bf5766743ba3"},{"sha":"5ca991392ffc8fb1aaff9008fb3a2471ce578120","author":{"email":"0c2ee2d5dadd96d6835a7124a25cb913bf474f64@marvell.com","name":"Jingju Hou"},"message":"mmc: sdhci-pxav3: fix platform_data is not initialized\n\ncommit 9cd76049f0d90ae241f5ad80e311489824527000 upstream.\n\npdev->dev.platform_data is not initialized if match is true in function\nsdhci_pxav3_probe. Just local variable pdata is assigned the return value\nfrom function pxav3_get_mmc_pdata().\n\nstatic int sdhci_pxav3_probe(struct platform_device *pdev) {\n\n    struct sdhci_pxa_platdata *pdata = pdev->dev.platform_data;\n    ...\n    if (match) {\n\t\tret = mmc_of_parse(host->mmc);\n\t\tif (ret)\n\t\t\tgoto err_of_parse;\n\t\tsdhci_get_of_property(pdev);\n\t\tpdata = pxav3_get_mmc_pdata(dev);\n     }\n     ...\n}\n\nSigned-off-by: Jingju Hou <houjingj@marvell.com>\nFixes: b650352dd3df(\"mmc: sdhci-pxa: Add device tree support\")\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/5ca991392ffc8fb1aaff9008fb3a2471ce578120"},{"sha":"103c46c95b48b228c98a8751726ab3bd9e90b525","author":{"email":"671da3e274b6e69bd6120633f915f839d634d12f@gmail.com","name":"Antonio Borneo"},"message":"HID: cp2112: fix to force single data-report reply\n\ncommit 6debce6f4e787a8eb4cec94e7afa85fb4f40db27 upstream.\n\nCurrent implementation of cp2112_raw_event() only accepts one data report at a\ntime. If last received data report is not fully handled yet, a new incoming\ndata report will overwrite it. In such case we don't guaranteed to propagate\nthe correct incoming data.\n\nThe trivial fix implemented here forces a single report at a time by requesting\nin cp2112_read() no more than 61 byte of data, which is the payload size of a\nsingle data report.\n\nSigned-off-by: Antonio Borneo <borneo.antonio@gmail.com>\nTested-by: Ellen Wang <ellen@cumulusnetworks.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/103c46c95b48b228c98a8751726ab3bd9e90b525"},{"sha":"bed0400e01d7ade4be054c909817fd1d3a591012","author":{"email":"643a80aaf16a8332d6a70921c14d4bb265446494@intel.com","name":"Emmanuel Grumbach"},"message":"iwlwifi: mvm: fix antenna selection when BT is active\n\ncommit 923a8c1d8069104726bde55c37cec66324ccc328 upstream.\n\nWhen BT is active, we want to avoid the shared antenna for\nmanagement frame to make sure we don't disturb BT. There\nwas a bug in that code because it chose the antenna\nBIT(ANT_A) where ANT_A is already a bitmap (0x1). This\nmeans that the antenna chosen in the end was ANT_B.\nWhile this is not optimal on devices with 2 antennas (it'd\ndisturb BT), it is critical on single antenna devices like\n3160 which couldn't connect at all when BT was active.\n\nThis fixes:\nhttps://bugzilla.kernel.org/show_bug.cgi?id=97181\n\nFixes: 34c8b24ff284 (\"iwlwifi: mvm: BT Coex - avoid the shared antenna for management frames\")\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/bed0400e01d7ade4be054c909817fd1d3a591012"},{"sha":"a8bc0fe729d868ffec8a1050925da446da32a01e","author":{"email":"30d0a3ea07b25a90f61a738417c75a14d6abc5ff@intel.com","name":"Liad Kaufman"},"message":"iwlwifi: nvm: remove mac address byte swapping in 8000 family\n\ncommit be88a1ada9b97bb016196b7f4a1fc2fe2f798529 upstream.\n\nThis fixes the byte order copying in the MAO (Mac Override\nSection) section from the PNVM, as the byte swapping is not\nrequired anymore in the 8000 family. Due to the byte\nswapping, the driver was reporting an incorrect MAC\nadddress.\n\nSigned-off-by: Liad Kaufman <liad.kaufman@intel.com>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/a8bc0fe729d868ffec8a1050925da446da32a01e"},{"sha":"5c5aba569ebf67a8bad4bf258af4111e42101654","author":{"email":"643a80aaf16a8332d6a70921c14d4bb265446494@intel.com","name":"Emmanuel Grumbach"},"message":"iwlwifi: pcie: prepare the device before accessing it\n\ncommit f9e5554cd8ca1d1212ec922755b397a20f737923 upstream.\n\nFor 8000 series, we need to access the device to know what\nfirmware to load. Before we do so, we need to prepare the\ndevice otherwise we might not be able to access the\nhardware.\n\nFixes: c278754a21e6 (\"iwlwifi: mvm: support family 8000 B2/C steps\")\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/5c5aba569ebf67a8bad4bf258af4111e42101654"},{"sha":"4731b65de6b30b7a8e771c51e4fb4a53846f158e","author":{"email":"1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.com","name":"NeilBrown"},"message":"md/raid1: fix test for 'was read error from last working device'.\n\ncommit 34cab6f42003cb06f48f86a86652984dec338ae9 upstream.\n\nWhen we get a read error from the last working device, we don't\ntry to repair it, and don't fail the device.  We simple report a\nread error to the caller.\n\nHowever the current test for 'is this the last working device' is\nwrong.\nWhen there is only one fully working device, it assumes that a\nnon-faulty device is that device.  However a spare which is rebuilding\nwould be non-faulty but so not the only working device.\n\nSo change the test from \"!Faulty\" to \"In_sync\".  If ->degraded says\nthere is only one fully working device and this device is in_sync,\nthis must be the one.\n\nThis bug has existed since we allowed read_balance to read from\na recovering spare in v3.0\n\nReported-and-tested-by: Alexander Lyakas <alex.bolshoy@gmail.com>\nFixes: 76073054c95b (\"md/raid1: clean up read_balance.\")\nSigned-off-by: NeilBrown <neilb@suse.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/4731b65de6b30b7a8e771c51e4fb4a53846f158e"},{"sha":"19ea7491d0b3555c333ceacaf489c51fa3d6e89e","author":{"email":"a4a57e4704114c949e291df12162e43868e17cb4@imgtec.com","name":"Sifan Naeem"},"message":"spi: img-spfi: fix support for speeds up to 1/4th input clock\n\ncommit 6a806a214af42ac951e2d85e64d1bf4463482e16 upstream.\n\nSetting the Same Edge bit indicates to the spfi block to receive and\ntransmit data on the same edge of the spfi clock, which in turn\ndoubles the operating frequency of spfi.\n\nThe maximum supported frequency is limited to 1/4th of the spfi input\nclock, but without this bit set the maximum would be 1/8th of the\ninput clock.\n\nThe current driver calculates the divisor with maximum speed at 1/4th\nof the input clock, this would fail if the requested frequency is\nhigher than 1/8 of the input clock. Any requests for 1/8th of the\ninput clock would still pass.\n\nFixes: 8543d0e72d43 (\"spi: img-spfi: Limit bit clock to 1/4th of input clock\")\nSigned-off-by: Sifan Naeem <sifan.naeem@imgtec.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/19ea7491d0b3555c333ceacaf489c51fa3d6e89e"},{"sha":"56e8479a04db9085278e17e0eac594927d327c5d","author":{"email":"c00cbc2b736c26791a3822db86f8796fe9efff67@pengutronix.de","name":"Sascha Hauer"},"message":"spi: imx: Fix small DMA transfers\n\ncommit f6ee9b582d2db652497b73c1f117591dfb6d3a90 upstream.\n\nDMA transfers must be greater than the watermark level size. spi_imx->rx_wml\nand spi_imx->tx_wml contain the watermark level in 32bit words whereas struct\nspi_transfer contains the transfer len in bytes. Fix the check if DMA is\npossible for a transfer accordingly. This fixes transfers with sizes between\n33 and 128 bytes for which previously was claimed that DMA is possible.\n\nFixes: f62caccd12c17e4 (spi: spi-imx: add DMA support)\nSigned-off-by: Sascha Hauer <s.hauer@pengutronix.de>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/56e8479a04db9085278e17e0eac594927d327c5d"},{"sha":"bec2057fee79fe271a629c98feb2201faba4ff2c","author":{"email":"074881f6f5da4d3b5278870ff234d1077ee622c0@ezchip.com","name":"Chris Metcalf"},"message":"tile: use free_bootmem_late() for initrd\n\ncommit 3f81d2447b37ac697b3c600039f2c6b628c06e21 upstream.\n\nWe were previously using free_bootmem() and just getting lucky\nthat nothing too bad happened.\n\nSigned-off-by: Chris Metcalf <cmetcalf@ezchip.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/bec2057fee79fe271a629c98feb2201faba4ff2c"},{"sha":"106c930a30784cb783b8ad9d4e685fd1d0c0cbe7","author":{"email":"4158a06f8b1a14710fca37e7bb2f120908ad440d@bytecmed.com","name":"Bernhard Bender"},"message":"Input: usbtouchscreen - avoid unresponsive TSC-30 touch screen\n\ncommit 968491709e5b1aaf429428814fff3d932fa90b60 upstream.\n\nThis patch fixes a problem in the usbtouchscreen driver for DMC TSC-30\ntouch screen.  Due to a missing delay between the RESET and SET_RATE\ncommands, the touch screen may become unresponsive during system startup or\ndriver loading.\n\nAccording to the DMC documentation, a delay is needed after the RESET\ncommand to allow the chip to complete its internal initialization. As this\ndelay is not guaranteed, we had a system where the touch screen\noccasionally did not send any touch data. There was no other indication of\nthe problem.\n\nThe patch fixes the problem by adding a 150ms delay between the RESET and\nSET_RATE commands.\n\nSuggested-by: Jakob Mustafa <jakob.mustafa@bytecmed.com>\nSigned-off-by: Bernhard Bender <bernhard.bender@bytecmed.com>\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/96boards/linux/commits/106c930a30784cb783b8ad9d4e685fd1d0c0cbe7"},{"sha":"1fbb15f220a6740327764b3775566771a4746fe6","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"blkcg: fix gendisk reference leak in blkg_conf_prep()\n\ncommit 5f6c2d2b7dbb541c1e922538c49fa04c494ae3d7 upstream.\n\nWhen a blkcg configuration is targeted to a partition rather than a\nwhole device, blkg_conf_prep fails with -EINVAL; unfortunately, it\nforgets to put the gendisk ref in that case.  Fix it.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nSigned-off-by: Jens Axboe <axboe@fb.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/1fbb15f220a6740327764b3775566771a4746fe6"},{"sha":"e4cadcc1c4595b336d7f9f9b1fb51c5afdf9a6f5","author":{"email":"1a8531307367602b8284517edb33d53d54e5ce8e@samsung.com","name":"Krzysztof Kozlowski"},"message":"regulator: s2mps11: Fix GPIO suspend enable shift wrapping bug\n\ncommit 32c848e33ace75fce388cceff76223d12b46eaa3 upstream.\n\nStatus of enabling suspend mode for regulator was stored in bitmap-like\nlong integer.\n\nHowever since adding support for S2MPU02 the number of regulators\nexceeded 32 so on devices with more than 32 regulators (S2MPU02 and\nS2MPS13) overflow happens when shifting the bit. This could lead to\nenabling suspend mode for completely different regulator than intended\nor to switching different regulator to other mode (e.g. from always\nenabled to controlled by PWRHOLD pin). Both cases could result in larger\nenergy usage and issues when suspending to RAM.\n\nFixes: 00e2573d2c10 (\"regulator: s2mps11: Add support S2MPU02 regulator device\")\nReported-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/e4cadcc1c4595b336d7f9f9b1fb51c5afdf9a6f5"},{"sha":"33f293b92e35ae208aefccdca05bcc268e03e4d2","author":{"email":"30ea2d6de7db423b663e964abd9bbdb7979e47a5@marvell.com","name":"Lior Amsalem"},"message":"ata: pmp: add quirk for Marvell 4140 SATA PMP\n\ncommit 945b47441d83d2392ac9f984e0267ad521f24268 upstream.\n\nThis commit adds the necessary quirk to make the Marvell 4140 SATA PMP\nwork properly. This PMP doesn't like SRST on port number 4 (the host\nport) so this commit marks this port as not supporting SRST.\n\nSigned-off-by: Lior Amsalem <alior@marvell.com>\nReviewed-by: Nadav Haklai <nadavh@marvell.com>\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nSigned-off-by: Tejun Heo <tj@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/33f293b92e35ae208aefccdca05bcc268e03e4d2"},{"sha":"6cf671f37e11f4b1b32f6cb2c6094dd923bcce4f","author":{"email":"bfee72d94d376f4e00f72b756466867d7f9eb24e@suse.com","name":"Oliver Neukum"},"message":"usb-storage: ignore ZTE MF 823 card reader in mode 0x1225\n\ncommit 5fb2c782f451a4fb9c19c076e2c442839faf0f76 upstream.\n\nThis device automatically switches itself to another mode (0x1405)\nunless the specific access pattern of Windows is followed in its\ninitial mode. That makes a dirty unmount of the internal storage\ndevices inevitable if they are mounted. So the card reader of\nsuch a device should be ignored, lest an unclean removal become\ninevitable.\n\nThis replaces an earlier patch that ignored all LUNs of this device.\nThat patch was overly broad.\n\nSigned-off-by: Oliver Neukum <oneukum@suse.com>\nReviewed-by: Lars Melin <larsm17@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/6cf671f37e11f4b1b32f6cb2c6094dd923bcce4f"},{"sha":"4eede03b97bf6d89681905668e983f99b5847827","author":{"email":"aa743a0aaec8f7d7a1f01442503957f4d7a2d634@protonic.nl","name":"David Jander"},"message":"Revert \"serial: imx: initialized DMA w/o HW flow enabled\"\n\ncommit 907eda32a36fcdb979bdb91ea097abb3dd2c23c9 upstream.\n\nThis reverts commit 068500e08dc87ea9a453cc4a500cf3ab28d0f936.\n\nAccording to some tests, SDMA support is broken at least for i.MX6 without\nHW flow control. Different forms of data-corruption appear either with\nthe ROM firmware for the SDMA controller as well as when loading Freescale\nprovided SDMA firmware versions 1.1 or 3.1.\n\nSigned-off-by: David Jander <david@protonic.nl>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/4eede03b97bf6d89681905668e983f99b5847827"},{"sha":"df86527517e8cd14f7ebec7302e70590543a49b5","author":{"email":"4b8373d016f277527198385ba72fda0feb5da015@hurleysoftware.com","name":"Peter Hurley"},"message":"serial: core: Fix crashes while echoing when closing\n\ncommit e144c58cad6667876173dd76977e9e6557e34941 upstream.\n\nWhile closing, new rx data may be received after the input buffers\nhave been flushed but before stop_rx() halts receiving [1]. The\nnew data might not be processed by flush_to_ldisc() until after\nuart_shutdown() and normal input processing is re-enabled (ie.,\ntty->closing = 0). The race is outlined below:\n\nCPU 0                         | CPU 1\n                              |\nuart_close()                  |\n   tty_port_close_start()     |\n      tty->closing = 1        |\n      tty_ldisc_flush()       |\n                              | => IRQ\n                              |   while (LSR & data ready)\n                              |      uart_insert_char()\n                              |   tty_flip_buffer_push()\n                              | <= EOI\n   stop_rx()                  |   .\n   uart_shutdown()            |   .\n      free xmit.buf           |   .\n   tty_port_tty_set(NULL)     |   .\n   tty->closing = 0           |   .\n                              | flush_to_ldisc()\n                              |   n_tty_receive_buf_common()\n                              |      __receive_buf()\n                              |         ...\n                              |         commit_echoes()\n                              |            uart_flush_chars()\n                              |               __uart_start()\n                              | ** OOPS on port.tty deref **\n   tty_ldisc_flush()          |\n\nInput processing must be prevented from echoing (tty->closing = 1)\nuntil _after_ the input buffers have been flushed again at the end\nof uart_close().\n\n[1] In fact, some input may actually be buffered _after_ stop_rx()\nsince the rx interrupt may have already triggered but not yet been\nhandled when stop_rx() disables rx interrupts.\n\nFixes: 2e758910832d (\"serial: core: Flush ldisc after dropping port\nmutex in uart_close()\")\nReported-by: Robert Elliott <elliott@hp.com>\nSigned-off-by: Peter Hurley <peter@hurleysoftware.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/96boards/linux/commits/df86527517e8cd14f7ebec7302e70590543a49b5"},{"sha":"eb9a669517a2eeb2e55fff733191c128b2f55830","author":{"email":"86906f747daba0f23da34ba3304b3b2c44118899@z273.org.uk","name":"Brian Campbell"},"message":"xhci: Calculate old endpoints correctly on device reset\n\ncommit 326124a027abc9a7f43f72dc94f6f0f7a55b02b3 upstream.\n\nWhen resetting a device the number of active TTs may need to be\ncorrected by xhci_update_tt_active_eps, but the number of old active\nendpoints supplied to it was always zero, so the number of TTs and the\nbandwidth reserved for them was not updated, and could rise\nunnecessarily.\n\nThis affected systems using Intel's Patherpoint chipset, which rely on\nsoftware bandwidth checking.  For example, a Lenovo X230 would lose the\nability to use ports on the docking station after enough suspend/resume\ncycles because the bandwidth calculated would rise with every cycle when\na suitable device is attached.\n\nThe correct number of active endpoints is calculated in the same way as\nin xhci_reserve_bandwidth.\n\nSigned-off-by: Brian Campbell <bacam@z273.org.uk>\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/96boards/linux/commits/eb9a669517a2eeb2e55fff733191c128b2f55830"},{"sha":"6f0433c52944a822f338f300fff672fa2fd43ac5","author":{"email":"5c5a6f60ec85c91f4d104324b41dbbaa93824778@intel.com","name":"Zhuang Jin Can"},"message":"xhci: report U3 when link is in resume state\n\ncommit 243292a2ad3dc365849b820a64868927168894ac upstream.\n\nxhci_hub_report_usb3_link_state() returns pls as U0 when the link\nis in resume state, and this causes usb core to think the link is in\nU0 while actually it's in resume state. When usb core transfers\ncontrol request on the link, it fails with TRB error as the link\nis not ready for transfer.\n\nTo fix the issue, report U3 when the link is in resume state, thus\nusb core knows the link it's not ready for transfer.\n\nSigned-off-by: Zhuang Jin Can <jin.can.zhuang@intel.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/96boards/linux/commits/6f0433c52944a822f338f300fff672fa2fd43ac5"}]}