{"push_id":1187275777,"size":377,"distinct_size":0,"ref":"refs/heads/netboot","head":"1f352efae26b3adb81097055406dccc2b511a63d","before":"16bfd9882b1be08b27a24d4618e8384d4400c96b","commits":[{"sha":"bea8205feeb1d28841541814ae375defb5b1986b","author":{"name":"Mark Brown","email":"bf2c7ef56f4d087c7cc4d81e9839c8674e3b6b2e@kernel.org"},"message":"Merge branch 'asoc-fix-ep93xx' into spi-fix-ep93xx","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/bea8205feeb1d28841541814ae375defb5b1986b"},{"sha":"b00c52dae6d9ee8d0f2407118ef6544ae5524781","author":{"name":"Wenwei Tao","email":"0e72ee3013ec017755f9dc9cfdf29e38735cbb85@gmail.com"},"message":"cgroup: remove redundant cleanup in css_create\n\nWhen create css failed, before call css_free_rcu_fn, we remove the css\nid and exit the percpu_ref, but we will do these again in\ncss_free_work_fn, so they are redundant.  Especially the css id, that\nwould cause problem if we remove it twice, since it may be assigned to\nanother css after the first remove.\n\ntj: This was broken by two commits updating the free path without\n    synchronizing the creation failure path.  This can be easily\n    triggered by trying to create more than 64k memory cgroups.\n\nSigned-off-by: Wenwei Tao <ww.tao0320@gmail.com>\nSigned-off-by: Tejun Heo <tj@kernel.org>\nCc: Vladimir Davydov <vdavydov@parallels.com>\nFixes: 9a1049da9bd2 (\"percpu-refcount: require percpu_ref to be exited explicitly\")\nFixes: 01e586598b22 (\"cgroup: release css->id after css_free\")\nCc: stable@vger.kernel.org # v3.17+","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/b00c52dae6d9ee8d0f2407118ef6544ae5524781"},{"sha":"595144c1141c951a3c6bb9004ae6a2bc29aad66f","author":{"name":"Heiko Stuebner","email":"f67af7135bf5422071c7efd95ce8a74473489823@sntech.de"},"message":"clk: rockchip: initialize flags of clk_init_data in mmc-phase clock\n\nThe flags element of clk_init_data was never initialized for mmc-\nphase-clocks resulting in the element containing a random value\nand thus possibly enabling unwanted clock flags.\n\nFixes: 89bf26cbc1a0 (\"clk: rockchip: Add support for the mmc clock phases using the framework\")\nCc: stable@vger.kernel.org\nSigned-off-by: Heiko Stuebner <heiko@sntech.de>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/595144c1141c951a3c6bb9004ae6a2bc29aad66f"},{"sha":"176df69cb080c8cd813e51f800069e13ee607641","author":{"name":"Brian Norris","email":"6171de59f5d877bdf30f45ca152231ebf21255a1@chromium.org"},"message":"clk: rockchip: mark rk3399 GIC clocks as critical\n\nWe never want to kill the GIC.\n\nNoticed when making other clock fixups, and seeing the newly-constructed\nclock tree try to disable cpll, where we had this parent structure:\n\n  aclk_gic <------\\\n                  |--- aclk_gic_pre <-- cpll <-- pll_cpll\n  aclk_gic_noc <--/\n\nSigned-off-by: Brian Norris <briannorris@chromium.org>\nReviewed-by: Douglas Anderson <dianders@chromium.org>\nSigned-off-by: Heiko Stuebner <heiko@sntech.de>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/176df69cb080c8cd813e51f800069e13ee607641"},{"sha":"3bd14ae9da9194d369334556a70a7ff73ef94491","author":{"name":"Xing Zheng","email":"2bdfef9cb1295ebcc2755d42cb44bb943abaa9f5@rock-chips.com"},"message":"clk: rockchip: fix incorrect parent for rk3399's {c,g}pll_aclk_perihp_src\n\nThere was a typo, swapping 'c' <--> 'g'.\n\nSigned-off-by: Xing Zheng <zhengxing@rock-chips.com>\nSigned-off-by: Brian Norris <briannorris@chromium.org>\nReviewed-by: Douglas Anderson <dianders@chromium.org>\nSigned-off-by: Heiko Stuebner <heiko@sntech.de>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/3bd14ae9da9194d369334556a70a7ff73ef94491"},{"sha":"4715f81afc342996f680b08c944a712d9cbef11b","author":{"name":"Douglas Anderson","email":"654d5d600e907ff4a0e75ec2e21c072be3e1556d@chromium.org"},"message":"clk: rockchip: Revert \"clk: rockchip: reset init state before mmc card initialization\"\n\nThis reverts commit 7a03fe6f48f3 (\"clk: rockchip: reset init state\nbefore mmc card initialization\").\n\nThough not totally obvious from the commit message nor from the source\ncode, that commit appears to be trying to reset the \"_drv\" MMC clocks to\n90 degrees (note that the \"_sample\" MMC clocks have a shift of 0 so are\nnot touched).\n\nThe major problem here is that it doesn't properly reset things.  The\nphase is a two bit field and the commit only touches one of the two\nbits.  Thus the commit had the following affect:\n- phase   0  => phase  90\n- phase  90  => phase  90\n- phase 180  => phase 270\n- phase 270  => phase 270\n\nThings get even weirder if you happen to have a bootloader that was\nactually using delay elements (should be no reason to, but you never\nknow), since those are additional bits that weren't touched by the\noriginal patch.\n\nThis is unlikely to be what we actually want.  Checking on rk3288-veyron\ndevices, I can see that the bootloader leaves these clocks as:\n- emmc:  phase 180\n- sdmmc: phase 90\n- sdio0: phase 90\n\nThus on rk3288-veyron devices the commit we're reverting had the effect\nof changing the eMMC clock to phase 270.  This probably explains the\nscattered reports I've heard of eMMC devices not working on some veyron\ndevices when using the upstream kernel.\n\nThe original commit was presumably made because previously the kernel\ndidn't touch the \"_drv\" phase at all and relied on whatever value was\nthere when the kernel started.  If someone was using a bootloader that\ntouched the \"_drv\" phase then, indeed, we should have code in the kernel\nto fix that.  ...and also, to get ideal timings, we should also have the\nkernel change the phase depending on the speed mode.  In fact, that's\nthe subject of a recent patch I posted at\n<https://patchwork.kernel.org/patch/9075141/>.\n\nIdeally, we should take both the patch posted to dw_mmc and this\nrevert.  Since those will likely go through different trees, here I\ndescribe behavior with the combos:\n\n1. Just this revert: likely will fix rk3288-veyron eMMC on some devices\n   + other cases; might break someone with a strange bootloader that\n   sets the phase to 0 or one that uses delay elements (pretty\n   unpredicable what would happen in that case).\n2. Just dw_mmc patch: fixes everyone.  Effectly the dw_mmc patch will\n   totally override the broken patch and fix everything.\n3. Both patches: fixes everyone.  Once dw_mmc is initting properly then\n   any defaults from the clock code doesn't mattery.\n\nFixes: 7a03fe6f48f3 (\"clk: rockchip: reset init state before mmc card initialization\")\nSigned-off-by: Douglas Anderson <dianders@chromium.org>\nReviewed-by: Shawn Lin <shawn.lin@rock-chips.com>\n\n[emmc and sdmmc still work on all current boards in mainline after this\nrevert, so they should take precedence over any out-of-tree board that\nwill hopefully again get fixed with the better upcoming dw_mmc change.]\nSigned-off-by: Heiko Stuebner <heiko@sntech.de>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/4715f81afc342996f680b08c944a712d9cbef11b"},{"sha":"3183c0d519ff83af2926382c11716496f01d34bf","author":{"name":"Xing Zheng","email":"2bdfef9cb1295ebcc2755d42cb44bb943abaa9f5@rock-chips.com"},"message":"clk: rockchip: fix cpuclk registration error handling\n\nIt maybe due to a copy-paste error the error handing should be\ncclk not clk when checking if the cpuclk registration succeeded.\n\nReported-by: Lin Huang <lin.huang@rock-chips.com>\nSigned-off-by: Xing Zheng <zhengxing@rock-chips.com>\nSigned-off-by: Heiko Stuebner <heiko@sntech.de>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/3183c0d519ff83af2926382c11716496f01d34bf"},{"sha":"3ac066e2227cb272c097f34475247fa0a6cdd2ff","author":{"name":"Jean-Jacques Hiblot","email":"57230d54682887a5030660f0d67327b9a3dfa1d8@ti.com"},"message":"spi: spi-ti-qspi: Suspend the queue before removing the device\n\nBefore disabling the pm_runtime, we must ensure that there is no transfer\nin progress nor will a new one be started. Otherwise the message pump will\nfail and in the end, the process requesting the transfer will be stuck.\nThis behavior has been observed when transferring data from a SPI flash\nwith dd while removing the module on a DRA7x-evm.\n\nSigned-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/3ac066e2227cb272c097f34475247fa0a6cdd2ff"},{"sha":"540c26087bfbad6ea72758b76b16ae6282a73fea","author":{"name":"Cameron Gutman","email":"dae64e07afda5ec299f6c7de821d7927f9ed1853@gmail.com"},"message":"Input: xpad - fix rumble on Xbox One controllers with 2015 firmware\n\nXbox One controllers that shipped with or were upgraded to the 2015\nfirmware discard the current rumble packets we send. This patch changes\nthe Xbox One rumble packet to a form that both the newer and older\nfirmware will accept.\n\nIt is based on changes made to support newer Xbox One controllers in\nthe SteamOS brewmaster-4.1 kernel branch.\n\nSigned-off-by: Cameron Gutman <aicommander@gmail.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/540c26087bfbad6ea72758b76b16ae6282a73fea"},{"sha":"62d0e71df063101e4551327bd9fa9aaa3535c86b","author":{"name":"Shawn Lin","email":"d05afb63fc7c176eb2c681ec3e64badcfb02edcb@rock-chips.com"},"message":"clk: rockchip: release io resource when failing to init clk on rk3399\n\nWe should call iounmap to relase reg_base since it's not going\nto be used any more if failing to init clk.\n\nThis was missing on the newly added rk3399 clock tree.\n\nSigned-off-by: Shawn Lin <shawn.lin@rock-chips.com>\nSigned-off-by: Heiko Stuebner <heiko@sntech.de>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/62d0e71df063101e4551327bd9fa9aaa3535c86b"},{"sha":"fee48cf8374569a3888fd8c8536283e6067f0cfb","author":{"name":"Ben Greear","email":"8607ce198d9f9074b7bb1e278bf7584a89ca2d9b@candelatech.com"},"message":"ath10k: fix deadlock when peer cannot be created\n\nWe must not attempt to send WMI packets while holding the data-lock,\nas it may deadlock:\n\nBUG: sleeping function called from invalid context at drivers/net/wireless/ath/ath10k/wmi.c:1824\nin_atomic(): 1, irqs_disabled(): 0, pid: 2878, name: wpa_supplicant\n\n=============================================\n[ INFO: possible recursive locking detected ]\n4.4.6+ #21 Tainted: G        W  O\n---------------------------------------------\nwpa_supplicant/2878 is trying to acquire lock:\n (&(&ar->data_lock)->rlock){+.-...}, at: [<ffffffffa0721511>] ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]\n\nbut task is already holding lock:\n (&(&ar->data_lock)->rlock){+.-...}, at: [<ffffffffa070251b>] ath10k_peer_create+0x122/0x1ae [ath10k_core]\n\nother info that might help us debug this:\n Possible unsafe locking scenario:\n\n       CPU0\n       ----\n  lock(&(&ar->data_lock)->rlock);\n  lock(&(&ar->data_lock)->rlock);\n\n *** DEADLOCK ***\n\n May be due to missing lock nesting notation\n\n4 locks held by wpa_supplicant/2878:\n #0:  (rtnl_mutex){+.+.+.}, at: [<ffffffff816493ca>] rtnl_lock+0x12/0x14\n #1:  (&ar->conf_mutex){+.+.+.}, at: [<ffffffffa0706932>] ath10k_add_interface+0x3b/0xbda [ath10k_core]\n #2:  (&(&ar->data_lock)->rlock){+.-...}, at: [<ffffffffa070251b>] ath10k_peer_create+0x122/0x1ae [ath10k_core]\n #3:  (rcu_read_lock){......}, at: [<ffffffffa062f304>] rcu_read_lock+0x0/0x66 [mac80211]\n\nstack backtrace:\nCPU: 3 PID: 2878 Comm: wpa_supplicant Tainted: G        W  O    4.4.6+ #21\nHardware name: To be filled by O.E.M. To be filled by O.E.M./ChiefRiver, BIOS 4.6.5 06/07/2013\n 0000000000000000 ffff8801fcadf8f0 ffffffff8137086d ffffffff82681720\n ffffffff82681720 ffff8801fcadf9b0 ffffffff8112e3be ffff8801fcadf920\n 0000000100000000 ffffffff82681720 ffffffffa0721500 ffff8801fcb8d348\nCall Trace:\n [<ffffffff8137086d>] dump_stack+0x81/0xb6\n [<ffffffff8112e3be>] __lock_acquire+0xc5b/0xde7\n [<ffffffffa0721500>] ? ath10k_wmi_tx_beacons_iter+0x15/0x11a [ath10k_core]\n [<ffffffff8112d0d0>] ? mark_lock+0x24/0x201\n [<ffffffff8112e908>] lock_acquire+0x132/0x1cb\n [<ffffffff8112e908>] ? lock_acquire+0x132/0x1cb\n [<ffffffffa0721511>] ? ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]\n [<ffffffffa07214eb>] ? ath10k_wmi_cmd_send_nowait+0x1ce/0x1ce [ath10k_core]\n [<ffffffff816f9e2b>] _raw_spin_lock_bh+0x31/0x40\n [<ffffffffa0721511>] ? ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]\n [<ffffffffa0721511>] ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]\n [<ffffffffa07214eb>] ? ath10k_wmi_cmd_send_nowait+0x1ce/0x1ce [ath10k_core]\n [<ffffffffa062eb18>] __iterate_interfaces+0x9d/0x13d [mac80211]\n [<ffffffffa062f609>] ieee80211_iterate_active_interfaces_atomic+0x32/0x3e [mac80211]\n [<ffffffffa07214eb>] ? ath10k_wmi_cmd_send_nowait+0x1ce/0x1ce [ath10k_core]\n [<ffffffffa071fa9f>] ath10k_wmi_tx_beacons_nowait.isra.13+0x14/0x16 [ath10k_core]\n [<ffffffffa0721676>] ath10k_wmi_cmd_send+0x71/0x242 [ath10k_core]\n [<ffffffffa07023f6>] ath10k_wmi_peer_delete+0x3f/0x42 [ath10k_core]\n [<ffffffffa0702557>] ath10k_peer_create+0x15e/0x1ae [ath10k_core]\n [<ffffffffa0707004>] ath10k_add_interface+0x70d/0xbda [ath10k_core]\n [<ffffffffa05fffcc>] drv_add_interface+0x123/0x1a5 [mac80211]\n [<ffffffffa061554b>] ieee80211_do_open+0x351/0x667 [mac80211]\n [<ffffffffa06158aa>] ieee80211_open+0x49/0x4c [mac80211]\n [<ffffffff8163ecf9>] __dev_open+0x88/0xde\n [<ffffffff8163ef6e>] __dev_change_flags+0xa4/0x13a\n [<ffffffff8163f023>] dev_change_flags+0x1f/0x54\n [<ffffffff816a5532>] devinet_ioctl+0x2b9/0x5c9\n [<ffffffff816514dd>] ? copy_to_user+0x32/0x38\n [<ffffffff816a6115>] inet_ioctl+0x81/0x9d\n [<ffffffff816a6115>] ? inet_ioctl+0x81/0x9d\n [<ffffffff81621cf8>] sock_do_ioctl+0x20/0x3d\n [<ffffffff816223c4>] sock_ioctl+0x222/0x22e\n [<ffffffff8121cf95>] do_vfs_ioctl+0x453/0x4d7\n [<ffffffff81625603>] ? __sys_recvmsg+0x4c/0x5b\n [<ffffffff81225af1>] ? __fget_light+0x48/0x6c\n [<ffffffff8121d06b>] SyS_ioctl+0x52/0x74\n [<ffffffff816fa736>] entry_SYSCALL_64_fastpath+0x16/0x7a\n\nSigned-off-by: Ben Greear <greearb@candelatech.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/fee48cf8374569a3888fd8c8536283e6067f0cfb"},{"sha":"8d0a0710ea0d22881fdb40eb79d346a98cc64ae6","author":{"name":"Ben Greear","email":"8607ce198d9f9074b7bb1e278bf7584a89ca2d9b@candelatech.com"},"message":"ath10k: fix crash related to printing features\n\nThis looks like a regression from commit c4cdf753ed42 (\"ath10k: move\nfw_features to struct ath10k_fw_file\"), we were printing the features from a\nwrong struct.\n\nFixes: c4cdf753ed42 (\"ath10k: move fw_features to struct ath10k_fw_file\")\nSigned-off-by:  Ben Greear <greearb@candelatech.com>\n[kvalo@qca.qualcomm.com: improve commit log]\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/8d0a0710ea0d22881fdb40eb79d346a98cc64ae6"},{"sha":"b36fad65d61fffe4b662d4bfb1ed673c455a36a2","author":{"name":"Michal Marek","email":"da90ea6f0836fa178971a89beee55a90b382acdd@suse.com"},"message":"kbuild: Initialize exported variables\n\nThe NOSTDINC_FLAGS variable is exported, so it needs to be cleared to\navoid duplicating its content when running make from within make (e.g.\nin the packaging targets). This became an issue after commit\n9c8fa9bc08f6 (\"kbuild: fix if_change and friends to consider argument\norder\"), which no longer ignores the duplicate options. As Paulo Zanoni\npoints out, the LDFLAGS_vmlinux variable has the same problem.\n\nReported-by: \"Zanoni, Paulo R\" <paulo.r.zanoni@intel.com>\nFixes: 9c8fa9bc08f6 (\"kbuild: fix if_change and friends to consider argument order\")\nSigned-off-by: Michal Marek <mmarek@suse.com>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/b36fad65d61fffe4b662d4bfb1ed673c455a36a2"},{"sha":"4dc0dd83603f05dc3ae152af33ecb15104c313f3","author":{"name":"Tomeu Vizoso","email":"05836fa86782885b94fac1506837be15b63cb13f@collabora.com"},"message":"spi: rockchip: Signal unfinished DMA transfers\n\nWhen using DMA, the transfer_one callback should return 1 because the\ntransfer hasn't finished yet.\n\nA previous commit changed the function to return 0 when the DMA channels\nwere correctly prepared.\n\nThis manifested in Veyron boards with this message:\n\n[ 1.983605] cros-ec-spi spi0.0: EC failed to respond in time\n\nFixes: ea9849113343 (\"spi: rockchip: check return value of dmaengine_prep_slave_sg\")\nSigned-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/4dc0dd83603f05dc3ae152af33ecb15104c313f3"},{"sha":"06a84db74c3572cde79eb1b04f301399eafb8226","author":{"name":"Luca Coelho","email":"907a6d4087ac6e6523ff3c213269cab2819d38b5@intel.com"},"message":"iwlwifi: mvm: increase scan timeout to 20 seconds\n\nThe 16 seconds timeout we were using turned out to be too short.\nRecalculations by system show that the total time in both bands should\nbe < 18.5 seconds, even in the slowest cases (e.g. DCM P2P with\nDTIM=2).  Rounding it up to 20 seconds for a bit more safety.\n\nFixes: 728e825f81b1 (\"iwlwifi: mvm: add a scan timeout for regular scans\")\nSigned-off-by: Luca Coelho <luciano.coelho@intel.com>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/06a84db74c3572cde79eb1b04f301399eafb8226"},{"sha":"7d6a1ab6a2db180122dee8db6c201f2dcf677813","author":{"name":"Emmanuel Grumbach","email":"8b9b3ed0afbc1fa5fc02c3dc29b7819d4e9d8433@intel.com"},"message":"iwlwifi: mvm: fix RCU splat in TKIP's update_key\n\nThe commit below mistakenly changed an rcu_dereference_check\nto a rcu_dereference_protected which introduced the\nfollowing RCU warning:\n\n[ INFO: suspicious RCU usage. ]\n 4.6.0-rc7-next-20160513-dbg-00004-g8de8b92-dirty #655 Not tainted\n -------------------------------\n drivers/net/wireless/intel/iwlwifi/mvm/mvm.h:1069 suspicious rcu_dereference_protected() usage!\n Call Trace:\n  [<ffffffff8106b836>] lockdep_rcu_suspicious+0xf7/0x100\n  [<ffffffffa03b2321>] iwl_mvm_get_key_sta.part.0+0x5d/0x80 [iwlmvm]\n  [<ffffffffa03b4acb>] iwl_mvm_update_tkip_key+0xd3/0x162 [iwlmvm]\n  [<ffffffffa03a2b60>] iwl_mvm_mac_update_tkip_key+0x17/0x19 [iwlmvm]\n  [<ffffffffa0329646>] ieee80211_tkip_decrypt_data+0x22c/0x24b [mac80211]\n  [<ffffffffa0318bb1>] ieee80211_crypto_tkip_decrypt+0xc5/0x110 [mac80211]\n  [<ffffffffa033102e>] ieee80211_rx_handlers+0x9bb/0x1fe1 [mac80211]\n\nFixes: 13303c0fb148 (\"iwlwifi: mvm: use helpers to get iwl_mvm_sta\")\nReported-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Luca Coelho <luciano.coelho@intel.com>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/7d6a1ab6a2db180122dee8db6c201f2dcf677813"},{"sha":"1f9788f335d7c3145bcb59bd570c5b9ef7203ef4","author":{"name":"Luca Coelho","email":"907a6d4087ac6e6523ff3c213269cab2819d38b5@intel.com"},"message":"iwlwifi: mvm: fix potential NULL-dereference in iwl_mvm_reorder()\n\nWe try to access sta before we check for IS_ERR_OR_NULL(), so we may\nend up accessing a NULL pointer.  To prevent that, move the conversion\nfrom sta to mvm_sta below the check.\n\nFixes: b915c10174fb (\"iwlwifi: mvm: add reorder buffer per queue\")\nReported-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Luca Coelho <luciano.coelho@intel.com>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/1f9788f335d7c3145bcb59bd570c5b9ef7203ef4"},{"sha":"aa950524d501afa28869b7f56e539fd9e744dd9f","author":{"name":"Ayala Beker","email":"49ee1b9c85578c58c7a5fea295a09aac9f12462d@intel.com"},"message":"iwlwifi: mvm: set the encryption type of an IGTK key\n\nThe FW expect the driver to set the encryption algorithm type when\ninstalling the IGTK key in the HW.\nCurrently when installing CMAC IGTK key we don't set the algorithm type\nand as a result the FW fails to calculate the MIC of multicast management\nframes.\nFix it.\n\nSigned-off-by: Ayala Beker <ayala.beker@intel.com>\nSigned-off-by: Luca Coelho <luciano.coelho@intel.com>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/aa950524d501afa28869b7f56e539fd9e744dd9f"},{"sha":"280a3efa82fccc9532c968a77e5162cb9f0af497","author":{"name":"Johannes Berg","email":"9a5936d824e6835dfe162c5611d10d2cf40ffbad@intel.com"},"message":"iwlwifi: mvm: fix a few firmware capability checks\n\nMy cleanup in \"iwlwifi: prepare for higher API/CAPA bits\" accidentally\ninverted a few tests - fix them.\n\nFixes: 859d914c8f5c (\"iwlwifi: prepare for higher API/CAPA bits\")\nReported-by: Sara Sharon <sara.sharon@intel.com>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Luca Coelho <luciano.coelho@intel.com>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/280a3efa82fccc9532c968a77e5162cb9f0af497"},{"sha":"fc0f7e3317c5f406e6d5520209b4689a4ffecfdf","author":{"name":"Manfred Schlaegl","email":"ca3723b6e6b7ac413cd05a659d7232ee8943b8d0@ginzinger.com"},"message":"net: phy: smsc: reintroduced unconditional soft reset\n\nWe detected some problems using the smsc lan8720a in combination with\ni.MX28 and tracked this down to commit 21009686662f (\"net: phy: smsc: move\nsmsc_phy_config_init reset part in a soft_reset function\")\nWith 2100968666 the generic soft reset is replaced by a specific function\nwhich handles power down state correctly. But additionally the soft reset\nitself got conditional and is therefore also only performed if the phy is\nin power down state.\n\nThis patch keeps the conditional wake up from power down, but\nre-introduces the unconditional soft reset using the generic soft reset\nfunction.\nIt was tested on linux-4.1.25 and linux-4.7.0-rc2.\n\nSigned-off-by: Manfred Schlaegl <manfred.schlaegl@ginzinger.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/andy-shev/linux/commits/fc0f7e3317c5f406e6d5520209b4689a4ffecfdf"}]}
{"actor":{"display_login":"andy-shev"}}