{"push_id":558715500,"size":105,"distinct_size":105,"ref":"refs/heads/master","head":"c59c961ca511dc7ee2f4f7e9c224d16f5c76ca6e","before":"26bc420b59a38e4e6685a73345a0def461136dce","commits":[{"sha":"ed9a84262a83ab0260325c2f5eae39e441003d55","author":{"email":"e5394ce9c4b9ae7d2c4686830c5ac5f3b9028b6a@free.fr","name":"Jean-Francois Moine"},"message":"drm: tda998x: Protect the page register\n\nAs the HDMI registers of the TDA998x chips are accessed by pages,\nthe page register must be protected.\n\nSigned-off-by: Jean-Francois Moine <moinejf@free.fr>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/ed9a84262a83ab0260325c2f5eae39e441003d55"},{"sha":"6833d26ef823b20acbf9d4afcfd7077e623b302c","author":{"email":"e5394ce9c4b9ae7d2c4686830c5ac5f3b9028b6a@free.fr","name":"Jean-Francois Moine"},"message":"drm: tda998x: Fix EDID read timeout on HDMI connect\n\nWhen the HDMI cable is disconnected and reconnected, EDID reading\nis called too early raising a EDID read timeout.\nThis patch uses the system work queue to delay the notification\nof the HDMI connect/disconnect event.\n\nSigned-off-by: Jean-Francois Moine <moinejf@free.fr>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/6833d26ef823b20acbf9d4afcfd7077e623b302c"},{"sha":"de3b7a06dfe15bda3e66a52285d422b954bb4832","author":{"email":"66deb1d63f85161cc287ce2bac0c65cb5ae958a7@secunet.com","name":"Steffen Klassert"},"message":"xfrm6: Fix transport header offset in _decode_session6.\n\nskb->transport_header might not be valid when we do a reverse\ndecode because the ipv6 tunnel error handlers don't update it\nto the inner transport header. This leads to a wrong offset\ncalculation and to wrong layer 4 informations. We fix this\nby using the size of the ipv6 header as the first offset.\n\nSigned-off-by: Steffen Klassert <steffen.klassert@secunet.com>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/de3b7a06dfe15bda3e66a52285d422b954bb4832"},{"sha":"f855691975bb06373a98711e4cfe2c224244b536","author":{"email":"66deb1d63f85161cc287ce2bac0c65cb5ae958a7@secunet.com","name":"Steffen Klassert"},"message":"xfrm6: Fix the nexthdr offset in _decode_session6.\n\nxfrm_decode_session() was originally designed for the\nusage in the receive path where the correct nexthdr offset\nis stored in IP6CB(skb)->nhoff. Over time this function\nspread to code that is used in the output path (netfilter,\nvti) where IP6CB(skb)->nhoff is not set. As a result, we\nget a wrong nexthdr and the upper layer flow informations\nare wrong. This can leed to incorrect policy lookups.\n\nSigned-off-by: Steffen Klassert <steffen.klassert@secunet.com>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/f855691975bb06373a98711e4cfe2c224244b536"},{"sha":"c957e8f084e0d21febcd6b8a0ea9631eccc92f36","author":{"email":"afb75201fb002d7fdd2b0b231e006999e00db8a9@linux.intel.com","name":"Mika Westerberg"},"message":"spi/pxa2xx: Clear cur_chip pointer before starting next message\n\nOnce the current message is finished, the driver notifies SPI core about\nthis by calling spi_finalize_current_message(). This function queues next\nmessage to be transferred. If there are more messages in the queue, it is\npossible that the driver is asked to transfer the next message at this\npoint.\n\nWhen spi_finalize_current_message() returns the driver clears the\ndrv_data->cur_chip pointer to NULL. The problem is that if the driver\nalready started the next message clearing drv_data->cur_chip will cause\nNULL pointer dereference which crashes the kernel like:\n\n BUG: unable to handle kernel NULL pointer dereference at 0000000000000048\n IP: [<ffffffffa0022bc8>] cs_deassert+0x18/0x70 [spi_pxa2xx_platform]\n PGD 78bb8067 PUD 37712067 PMD 0\n Oops: 0000 [#1] SMP\n Modules linked in:\n CPU: 1 PID: 11 Comm: ksoftirqd/1 Tainted: G           O   3.18.0-rc4-mjo #5\n Hardware name: Intel Corp. VALLEYVIEW B3 PLATFORM/NOTEBOOK, BIOS MNW2CRB1.X64.0071.R30.1408131301 08/13/2014\n task: ffff880077f9f290 ti: ffff88007a820000 task.ti: ffff88007a820000\n RIP: 0010:[<ffffffffa0022bc8>]  [<ffffffffa0022bc8>] cs_deassert+0x18/0x70 [spi_pxa2xx_platform]\n RSP: 0018:ffff88007a823d08  EFLAGS: 00010202\n RAX: 0000000000000008 RBX: ffff8800379a4430 RCX: 0000000000000026\n RDX: 0000000000000000 RSI: 0000000000000246 RDI: ffff8800379a4430\n RBP: ffff88007a823d18 R08: 00000000ffffffff R09: 000000007a9bc65a\n R10: 000000000000028f R11: 0000000000000005 R12: ffff880070123e98\n R13: ffff880070123de8 R14: 0000000000000100 R15: ffffc90004888000\n FS:  0000000000000000(0000) GS:ffff880079a80000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b\n CR2: 0000000000000048 CR3: 000000007029b000 CR4: 00000000001007e0\n Stack:\n  ffff88007a823d58 ffff8800379a4430 ffff88007a823d48 ffffffffa0022c89\n  0000000000000000 ffff8800379a4430 0000000000000000 0000000000000006\n  ffff88007a823da8 ffffffffa0023be0 ffff88007a823dd8 ffffffff81076204\n Call Trace:\n  [<ffffffffa0022c89>] giveback+0x69/0xa0 [spi_pxa2xx_platform]\n  [<ffffffffa0023be0>] pump_transfers+0x710/0x740 [spi_pxa2xx_platform]\n  [<ffffffff81076204>] ? pick_next_task_fair+0x744/0x830\n  [<ffffffff81049679>] tasklet_action+0xa9/0xe0\n  [<ffffffff81049a0e>] __do_softirq+0xee/0x280\n  [<ffffffff81049bc0>] run_ksoftirqd+0x20/0x40\n  [<ffffffff810646df>] smpboot_thread_fn+0xff/0x1b0\n  [<ffffffff810645e0>] ? SyS_setgroups+0x150/0x150\n  [<ffffffff81060f9d>] kthread+0xcd/0xf0\n  [<ffffffff81060ed0>] ? kthread_create_on_node+0x180/0x180\n  [<ffffffff8187a82c>] ret_from_fork+0x7c/0xb0\n\nFix this by clearing drv_data->cur_chip before we call spi_finalize_current_message().\n\nReported-by: Martin Oldfield <m@mjoldfield.com>\nSigned-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>\nAcked-by: Robert Jarzmik <robert.jarzmik@free.fr>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/c957e8f084e0d21febcd6b8a0ea9631eccc92f36"},{"sha":"d297933cc7fcfbaaf2d37570baac73287bf0357d","author":{"email":"b6ffd6973e972cb999e8e535ab74da7fee0c035f@ingics.com","name":"Axel Lin"},"message":"spi: dw: Fix detecting FIFO depth\n\nCurrent code tries to find the highest valid fifo depth by checking the value\nit wrote to DW_SPI_TXFLTR. There are a few problems in current code:\n1) There is an off-by-one in dws->fifo_len setting because it assumes the latest\n   register write fails so the latest valid value should be fifo - 1.\n2) We know the depth could be from 2 to 256 from HW spec, so it is not necessary\n   to test fifo == 257. In the case fifo is 257, it means the latest valid\n   setting is fifo = 256. So after the for loop iteration, we should check\n   fifo == 2 case instead of fifo == 257 if detecting the FIFO depth fails.\nThis patch fixes above issues.\n\nSigned-off-by: Axel Lin <axel.lin@ingics.com>\nReviewed-and-tested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/d297933cc7fcfbaaf2d37570baac73287bf0357d"},{"sha":"67bf9cda4b498b8cea4a40be67a470afe57d2e88","author":{"email":"74f0c009df510614346aa771cd21959b78cdb413@linux.intel.com","name":"Andy Shevchenko"},"message":"spi: dw-mid: fix FIFO size\n\nThe FIFO size is 40 accordingly to the specifications, but this means 0x40,\ni.e. 64 bytes. This patch fixes the typo and enables FIFO size autodetection\nfor Intel MID devices.\n\nFixes: 7063c0d942a1 (spi/dw_spi: add DMA support)\nSigned-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/67bf9cda4b498b8cea4a40be67a470afe57d2e88"},{"sha":"6d40530e4789b3e2f14d61ca57ab02bd5395d5c9","author":{"email":"de6fb888308c49c20838826baf4e7cc406af80ff@renesas.com","name":"Yoshihiro Shimoda"},"message":"spi: sh-msiof: fix MDR1_FLD_MASK value\n\nSince the FLD bit field is bit[3:2], the MDR1_FLD_MASK value should\nbe 0x0000000c.\n\nSigned-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>\nAcked-by: Geert Uytterhoeven <geert+renesas@glider.be>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/6d40530e4789b3e2f14d61ca57ab02bd5395d5c9"},{"sha":"3dbb3b98e854bceed38fbde930fb8cf8701def73","author":{"email":"74f0c009df510614346aa771cd21959b78cdb413@linux.intel.com","name":"Andy Shevchenko"},"message":"spi: dw: amend warning message\n\nIn case of warning message in ->probe() we have to use HW device name instead\nof master because last is not defined yet.\n\nSigned-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/3dbb3b98e854bceed38fbde930fb8cf8701def73"},{"sha":"83b0302d347a49f951e904184afe57ac3723476e","author":{"email":"221b44264b34c4c2680fd1c85801ea1a2d0a4da6@codeaurora.org","name":"Ashay Jaiswal"},"message":"regulator: core: fix race condition in regulator_put()\n\nThe regulator framework maintains a list of consumer regulators\nfor a regulator device and protects it from concurrent access using\nthe regulator device's mutex lock.\n\nIn the case of regulator_put() the consumer is removed and regulator\ndevice's parameters are updated without holding the regulator device's\nmutex. This would lead to a race condition between the regulator_put()\nand any function which traverses the consumer list or modifies regulator\ndevice's parameters.\nFix this race condition by holding the regulator device's mutex in case\nof regulator_put.\n\nSigned-off-by: Ashay Jaiswal <ashayj@codeaurora.org>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/83b0302d347a49f951e904184afe57ac3723476e"},{"sha":"ad26aa6c60974acf3228ed0ade97ba5793093dbe","author":{"email":"41b6036433e5f6e320aceb7f1267c6aae8cab431@samsung.com","name":"Jonghwa Lee"},"message":"regulator: s2mps11: Fix wrong calculation of register offset\n\nThis patch adds missing registers('BUCK7_SW' & 'LDO29_CTRL'). Since BUCK7 has\n1 more register (BUCK7_SW) than others, register offset should\nbe added one more for which has bigger address than BUCK7 registers.\n\nFixes: 76b9840b24ae04(regulator: s2mps11: Add support S2MPS13 regulator device)\nSigned-off-by: Jonghwa Lee <jonghwa3.lee@samsung.com>\nSigned-off-by: Chanwoo Choi <cw00.choi@samsung.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: <stable@vger.kernel.org>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/ad26aa6c60974acf3228ed0ade97ba5793093dbe"},{"sha":"1f9c418fd94c97c82dc0454fdadece37238f23e7","author":{"email":"fd1202a3583a2c18280b3ee0868e57d89bacc3b6@intel.com","name":"David Spinadel"},"message":"iwlwifi: mvm: fix EBS on single scan\n\nEBS error detection isn't supported by all FWs, so turn it on\nonly if the FW advertises such support.\n\nSigned-off-by: David Spinadel <david.spinadel@intel.com>\nReviewed-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/1f9c418fd94c97c82dc0454fdadece37238f23e7"},{"sha":"4e6c48e0984e28d064ee8fbc292aee7b7920c507","author":{"email":"643a80aaf16a8332d6a70921c14d4bb265446494@intel.com","name":"Emmanuel Grumbach"},"message":"iwlwifi: mvm: drop non VO frames when flushing\n\nThis change has already been implemented in iwldvm:\n\ncommit a260e7b3f0307878b99d57ed1406cf2d497923b8\nAuthor: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nDate:   Sun Oct 5 09:11:14 2014 +0300\n\n    iwlwifi: dvm: drop non VO frames when flushing\n\nSince I added the flush() callback implementation in mvm,\nwe got reports that the queues are stuck while roaming\nor suspending.\nThis commit above helped much for iwldvm, implement the\nsame behavior for iwlmvm.\n\nCC: <stable@vger.kernel.org> [3.16+]\nFixes: c5b0e7c0565a (\"iwlwifi: mvm: implement mac80211's flush callback\")\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/4e6c48e0984e28d064ee8fbc292aee7b7920c507"},{"sha":"9b3b43d8d1300c36ba5945c12fd505409eaf4807","author":{"email":"3479a0d7b15002d26d6793122e309097153caf7e@wizery.com","name":"Eyal Shapira"},"message":"iwlwifi: mvm: set the tx cmd tid for BAR frame correctly\n\nBAR tx cmd tid was set to non qos (8). This is wrong as BAR\nshould be sent with the tid of the BA session.\nThis led to a corruption in the firmware. The visible\neffect of this from the driver side is the BA notification\nthat comes back after the BAR. It was botched and led to the\nWARNING below.\n\n------------[ cut here ]------------\nWARNING: CPU: 2 PID: 17707 at /home/tester/workspace_hostap/iwlwifi/drivers/net/wireless/iwlwifi/mvm/tx.c:976 iwl_mvm_rx_ba_notif+0x4ba/0x4d0 [iwlmvm]()\nQ 4500, tid 8, flow 65535\nModules linked in: iwlmvm(O) mac80211(O) iwlwifi(O) cfg80211(O) compat(O) netconsole configfs ctr ccm arc4 autofs4 microcode bnep rfcomm snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel joydev snd_hda_codec uvcvideo videobuf2_core snd_hwdep videodev snd_pcm videobuf2_vmalloc videobuf2_memops i915 snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device drm_kms_helper dell_wmi dell_laptop drm btusb bluetooth snd psmouse i2c_algo_bit sparse_keymap wmi soundcore 6lowpan_iphc dcdbas serio_raw video lpc_ich ppdev mac_hid parport_pc nfsd nfs_acl auth_rpcgss nfs fscache binfmt_misc lockd sunrpc lp parport msdos sdhci_pci sdhci mmc_core ahci libahci e1000e ptp pps_core [last unloaded: compat]\nCPU: 2 PID: 17707 Comm: irq/46-iwlwifi Tainted: G        W  O 3.14.17-patched #4\nHardware name: Dell Inc. Latitude E6430/0CPWYR, BIOS A09 12/13/2012\n 00000000 00000000 ebd49d6c c1616221 f985dbdc ebd49d9c c1044e44 f9861df4\n ebd49dc8 0000452b f985dbdc 000003d0 f98395da f98395da ebd49f10 eaf3d8a4\n 0000ffff ebd49db4 c1044f03 00000009 ebd49dac f9861df4 ebd49dc8 ebd49e64\nCall Trace:\n [<c1616221>] dump_stack+0x41/0x52\n [<c1044e44>] warn_slowpath_common+0x84/0xa0\n [<f98395da>] ? iwl_mvm_rx_ba_notif+0x4ba/0x4d0 [iwlmvm]\n [<f98395da>] ? iwl_mvm_rx_ba_notif+0x4ba/0x4d0 [iwlmvm]\n [<c1044f03>] warn_slowpath_fmt+0x33/0x40\n [<f98395da>] iwl_mvm_rx_ba_notif+0x4ba/0x4d0 [iwlmvm]\n [<c10e3952>] ? ring_buffer_unlock_commit+0xa2/0xd0\n [<c10e9767>] ? trace_buffer_unlock_commit+0x37/0x50\n [<f98568a3>] ? iwl_tm_mvm_send_rx+0x53/0x90 [iwlmvm]\n [<f98327a8>] iwl_mvm_rx_dispatch+0x108/0x130 [iwlmvm]\n [<f9eac7e7>] iwl_pcie_irq_handler+0xf17/0x15b0 [iwlwifi]\n [<c10994c1>] irq_thread_fn+0x21/0x50\n [<c109926c>] irq_thread+0xec/0x110\n [<c10994a0>] ? irq_thread_dtor+0xb0/0xb0\n [<c10993f0>] ? irq_finalize_oneshot.part.34+0xc0/0xc0\n [<c1099180>] ? wake_threads_waitq+0x40/0x40\n [<c1062fdb>] kthread+0x9b/0xb0\n [<c1627137>] ret_from_kernel_thread+0x1b/0x28\n [<c1062f40>] ? flush_kthread_worker+0x90/0x90\n---[ end trace 5e0f67374816db17 ]---\n\nSigned-off-by: Eyal Shapira <eyalx.shapira@intel.com>\nReviewed-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/9b3b43d8d1300c36ba5945c12fd505409eaf4807"},{"sha":"781f51d4c2038b694a774b070dcd93ea22d10655","author":{"email":"7081a7d99b8c74c0698a728df19e3915a995d7e1@codeaurora.org","name":"Kalle Valo"},"message":"Merge tag 'iwlwifi-for-kalle-2015-01-13' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes\n\n* A fix for scan that fixes a firmware assertion\n* A fix that improves roaming behavior. Same fix has been tested for\n  a while in iwldvm. This is a bit of a work around, but the real fix\n  should be in mac80211 and will come later.\n* A fix for BARs that avoids a WARNING.","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/781f51d4c2038b694a774b070dcd93ea22d10655"},{"sha":"f046bfdf735794d5893963427eb54302b7940a86","author":{"email":"7ad054068e22862b74505c1139ad54a17792b0d9@amd.com","name":"Ben Goz"},"message":"drm/amdkfd: PQM handle queue creation fault\n\nIf the first queue created was failed on DQM then PQM should\nunregister the process from DQM.\n\nSigned-off-by: Ben Goz <ben.goz@amd.com>\nSigned-off-by: Oded Gabbay <oded.gabbay@amd.com>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/f046bfdf735794d5893963427eb54302b7940a86"},{"sha":"d56133793a79153b7d8144d09ddeec17554ce190","author":{"email":"b51b9a92386687a9ac927cebfa0f978adeb8cea5@kernel.org","name":"Mark Brown"},"message":"Merge remote-tracking branch 'regulator/fix/core' into regulator-linus","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/d56133793a79153b7d8144d09ddeec17554ce190"},{"sha":"113620bb89a580d72a1dd78e677c0c8aac45cf0c","author":{"email":"b51b9a92386687a9ac927cebfa0f978adeb8cea5@kernel.org","name":"Mark Brown"},"message":"Merge remote-tracking branch 'regulator/fix/s2mps11' into regulator-linus","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/113620bb89a580d72a1dd78e677c0c8aac45cf0c"},{"sha":"b8cbab042cd69f3918a51620986514681c6cbad0","author":{"email":"c2fce4493a16d94b58efb315151c29911fc5d347@amd.com","name":"Oded Gabbay"},"message":"drm/amdkfd: Allow user to limit only queues per device\n\nThis patch replaces the two current amdkfd module parameters with a new one.\n\nThe current parameters that are being replaced are:\n\n- Maximum number of HSA processes\n- Maximum number of queues per process\n\nThe new parameter that replaces them is called \"Maximum queues per device\"\n\nThis replacement achieves two goals:\n\n- Allows the user to have as many HSA processes as it wants (until\n  a maximum of 512 HSA processes in Kaveri).\n\n- Removes the limitation the user had on maximum number of queues per HSA\n  process. E.g. the user can now have processes which only have one queue and\n  other processes which have hundreds of queues, while before the user\n  couldn't have more than 128 queues per process (as default).\n\nThe default value of the new parameter is 4096 (32 * 128, which were the\ndefaults of the old parameters). There is almost no additional GART memory\nrequired for the default case. As a reminder, this amount of queues requires a\nlittle bit below 4MB of GART memory.\n\nv2:\nIn addition, This patch defines a new counter for queues accounting in the DQM\nstructure. This is done because the current counter only counts active queues\nwhich allows the user to create more queues than the\nmax_num_of_queues_per_device module parameter allows.\n\nHowever, we need the current counter for the runlist packet build process, so\nthe solution is to have a dedicated counter for this accounting.\n\nSigned-off-by: Oded Gabbay <oded.gabbay@amd.com>\nReviewed-by: Ben Goz <ben.goz@amd.com>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/b8cbab042cd69f3918a51620986514681c6cbad0"},{"sha":"90ea15c1148bb1517e400ed14bb875e330aead2e","author":{"email":"643a80aaf16a8332d6a70921c14d4bb265446494@intel.com","name":"Emmanuel Grumbach"},"message":"iwlwifi: mvm: abort scheduled scan upon RFKILL\n\nWhen we have an active scheduled scan, and the RFKILL\ninterrupt kicks in, the stack will cancel the scheduled\nscan as part of the down flow. But cancelling scheduled\nscan usually implies sending a command to the firwmare\nwhich has been killed as part of the RFKILL interrupt\nhandling.\nBecause of that, we returned an error to mac80211 when\nit asked to stop the scheduled scan and didn't notify the\nend of the scheduled scan. Besides a fat warning, this led\nto a situation in which cfg80211 would refuse any new scan\nrequest.\n\nTo disentangle this, fake that the scheduled scan has been\nstopped without sending the command to the firwmare, return\n0 after having properly let cfg80211 know that the scan\nhas been cancelled.\n\nThis is basically the same as:\ncommit 9b520d84957d63348e87c0f2cbd21d86e1e8f2f2\nAuthor: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nDate:   Tue Nov 4 15:54:11 2014 +0200\n\n    iwlwifi: mvm: abort scan upon RFKILL\n\n    This code existed but not for all the different FW APIs\n    we support.\n    Fix this.\n\nbut for the scheduled scan case.\n\nLink: http://permalink.gmane.org/gmane.linux.kernel.wireless.general/133232\nReported-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>","distinct":true,"url":"https://api.github.com/repos/ZENOME/linux/commits/90ea15c1148bb1517e400ed14bb875e330aead2e"}]}