{"push_id":855050437,"size":1000,"distinct_size":8,"ref":"refs/heads/korg-wireless-testing/master","head":"b7da5ccdf418f418504e1c923e954ec8ff1a690c","before":"d5349dc67c283b94a01721f6d531f8d3dd5685d8","commits":[{"sha":"bcb9db49bb9da895ee809bfb2718d664dfb3ee2f","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"mlxsw: fix warnings for big-endian 32-bit dma_addr_t\n\nThe recently added mlxsw driver produces warnings in ARM\nallmodconfig:\n\ndrivers/net/ethernet/mellanox/mlxsw/pci.c: In function 'mlxsw_pci_cmd_exec':\ndrivers/net/ethernet/mellanox/mlxsw/pci.c:1585:59: warning: right shift count >= width of type [-Wshift-count-overflow]\nlinux/byteorder/big_endian.h:38:51: note: in definition of macro '__cpu_to_be32'\ndrivers/net/ethernet/mellanox/mlxsw/pci.c:76:2: note: in expansion of macro 'iowrite32be'\n\nThis uses upper_32_bits() to extract the bits while avoiding that warning.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nAcked-by: Jiri Pirko <jiri@mellanox.com>\nFixes: eda6500a987a \"mlxsw: Add PCI bus implementation\"\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/bcb9db49bb9da895ee809bfb2718d664dfb3ee2f"},{"sha":"9d3a6386c8238bfacf57ee9dac68ec4b40b302fe","author":{"email":"efca98801f3398ebd7eeff805a2c18e6c49e84d4@suse.de","name":"Jean Delvare"},"message":"net: mdio-octeon: Drop obsolete Kconfig advice\n\n\"Y\" was the right answer for MDIO_OCTEON when this option was only\navailable on CAVIUM_OCTEON_SOC. But now that the option is visible on\nall (64-bit) systems, this piece of advice no longer makes sense. This\nhelper module is selected automatically by drivers which need it\nanyway.\n\nSigned-off-by: Jean Delvare <jdelvare@suse.de>\nFixes: a6d6786452 (\"net: mdio-octeon: Modify driver to work on both ThunderX and Octeon\")\nCc: Florian Fainelli <f.fainelli@gmail.com>\nCc: Sunil Goutham <sgoutham@cavium.com>\nCc: Radha Mohan Chintakuntla <rchintakuntla@cavium.com>\nCc: David Daney <david.daney@cavium.com>\nCc: David S. Miller <davem@davemloft.net>\nAcked-by: David Daney <david.daney@cavium.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/9d3a6386c8238bfacf57ee9dac68ec4b40b302fe"},{"sha":"85121d6ee6973f98789bf7343f7f636c01e2de19","author":{"email":"85eaff3c03d4b4d3d601e96c3e1c7f9e58a5538d@linux.vnet.ibm.com","name":"Carol L Soto"},"message":"net/mlx4: Remove shared_ports variable at mlx4_enable_msi_x\n\nIf we get MAX_MSIX interrupts would like to have each receive ring\nwith his own msix interrupt line. Do not need the shared_ports\nvariable at mlx4_enable_msix\n\nFixes: 9293267a3e2a ('net/mlx4_core: Capping number of requested MSIXs to MAX_MSIX')\nSigned-off-by: Carol L Soto <clsoto@linux.vnet.ibm.com>\nAcked-by: Matan Barak <matanb@mellanox.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/85121d6ee6973f98789bf7343f7f636c01e2de19"},{"sha":"a66d7f724a96d6fd279bfbd2ee488def6b081bea","author":{"email":"d1e82e2813f00e3d60e00aa92378ef41c34f031b@oracle.com","name":"Dave Kleikamp"},"message":"crypto: sparc - initialize blkcipher.ivsize\n\nSome of the crypto algorithms write to the initialization vector,\nbut no space has been allocated for it. This clobbers adjacent memory.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/a66d7f724a96d6fd279bfbd2ee488def6b081bea"},{"sha":"92b279070dd6c94265db32748bbeb5b583588de9","author":{"email":"73675debcd8a436be48ec22211dcf44fe0df0a64@decadent.org.uk","name":"Ben Hutchings"},"message":"crypto: camellia_aesni_avx - Fix CPU feature checks\n\nWe need to explicitly check the AVX and AES CPU features, as we can't\ninfer them from the related XSAVE feature flags.  For example, the\nCore i3 2310M passes the XSAVE feature test but does not implement\nAES-NI.\n\nReported-and-tested-by: Stéphane Glondu <glondu@debian.org>\nReferences: https://bugs.debian.org/800934\nFixes: ce4f5f9b65ae (\"x86/fpu, crypto x86/camellia_aesni_avx: Simplify...\")\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nCc: stable <stable@vger.kernel.org> # 4.2\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/92b279070dd6c94265db32748bbeb5b583588de9"},{"sha":"7a574557e62dc3d2d7ed55fa0b99e7d5bb403878","author":{"email":"551ae05ce198473af5b9da594240f54df5f81e31@gmail.com","name":"Sudip Mukherjee"},"message":"drm/amdgpu: fix memory leak in amdgpu_vm_update_page_directory\n\nIf amdgpu_ib_get() fails we returned the error code but we missed\nfreeing ib.\n\nCc: \"Christian König\" <christian.koenig@amd.com>\nCc: Jammy Zhou <Jammy.Zhou@amd.com>\nCc: Chunming Zhou <david1.zhou@amd.com>\nCc: Alex Deucher <alexander.deucher@amd.com>\nCc: \"monk.liu\" <monk.liu@amd.com>\nSigned-off-by: Sudip Mukherjee <sudip@vectorindia.org>\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/7a574557e62dc3d2d7ed55fa0b99e7d5bb403878"},{"sha":"dcc909d90ccdbb73226397ff6d298f7af35b0e11","author":{"email":"b9e0f7aed71fa470d5913fb2df2da788a8fb0eb2@pengutronix.de","name":"Markus Pargmann"},"message":"nbd: Add locking for tasks\n\nThe timeout handling introduced in\n\t7e2893a16d3e (nbd: Fix timeout detection)\nintroduces a race condition which may lead to killing of tasks that are\nnot in nbd context anymore. This was not observed or reproducable yet.\n\nThis patch adds locking to critical use of task_recv and task_send to\navoid killing tasks that already left the NBD thread functions. This\nlock is only acquired if a timeout occures or the nbd device\nstarts/stops.\n\nReported-by: Ben Hutchings <ben@decadent.org.uk>\nSigned-off-by: Markus Pargmann <mpa@pengutronix.de>\nReviewed-by: Ben Hutchings <ben@decadent.org.uk>\nFixes: 7e2893a16d3e (\"nbd: Fix timeout detection\")\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/dcc909d90ccdbb73226397ff6d298f7af35b0e11"},{"sha":"fdf880a60835cd1dec2563463ac63ae3084e0ddc","author":{"email":"99dea9acac81454e66986aa60f5d078ee8370e4c@gmail.com","name":"Cyril Bur"},"message":"powerpc: Fix checkstop in native_hpte_clear() with lockdep\n\nnative_hpte_clear() is called in real mode from two places:\n- Early in boot during htab initialisation if firmware assisted dump is\n  active.\n- Late in the kexec path.\n\nIn both contexts there is no need to disable interrupts are they are\nalready disabled. Furthermore, locking around the tlbie() is only required\nfor pre POWER5 hardware.\n\nOn POWER5 or newer hardware concurrent tlbie()s work as expected and on pre\nPOWER5 hardware concurrent tlbie()s could result in deadlock. This code\nwould only be executed at crashdump time, during which all bets are off,\nconcurrent tlbie()s are unlikely and taking locks is unsafe therefore the\nbest course of action is to simply do nothing. Concurrent tlbie()s are not\npossible in the first case as secondary CPUs have not come up yet.\n\nSigned-off-by: Cyril Bur <cyrilbur@gmail.com>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/fdf880a60835cd1dec2563463ac63ae3084e0ddc"},{"sha":"f2dd80ecca5f06b46134f2bd811f046c503c756c","author":{"email":"cf1af486034ab0119a20f38a060e40da25f4cea3@axtens.net","name":"Daniel Axtens"},"message":"powerpc/powernv: Panic on unhandled Machine Check\n\nAll unrecovered machine check errors on PowerNV should cause an\nimmediate panic. There are 2 reasons that this is the right policy:\nit's not safe to continue, and we're already trying to reboot.\n\nFirstly, if we go through the recovery process and do not successfully\nrecover, we can't be sure about the state of the machine, and it is\nnot safe to recover and proceed.\n\nLinux knows about the following sources of Machine Check Errors:\n- Uncorrectable Errors (UE)\n- Effective - Real Address Translation (ERAT)\n- Segment Lookaside Buffer (SLB)\n- Translation Lookaside Buffer (TLB)\n- Unknown/Unrecognised\n\nIn the SLB, TLB and ERAT cases, we can further categorise these as\nparity errors, multihit errors or unknown/unrecognised.\n\nWe can handle SLB errors by flushing and reloading the SLB. We can\nhandle TLB and ERAT multihit errors by flushing the TLB. (It appears\nwe may not handle TLB and ERAT parity errors: I will investigate\nfurther and send a followup patch if appropriate.)\n\nThis leaves us with uncorrectable errors. Uncorrectable errors are\nusually the result of ECC memory detecting an error that it cannot\ncorrect, but they also crop up in the context of PCI cards failing\nduring DMA writes, and during CAPI error events.\n\nThere are several types of UE, and there are 3 places a UE can occur:\nSkiboot, the kernel, and userspace. For Skiboot errors, we have the\nfacility to make some recoverable. For userspace, we can simply kill\n(SIGBUS) the affected process. We have no meaningful way to deal with\nUEs in kernel space or in unrecoverable sections of Skiboot.\n\nCurrently, these unrecovered UEs fall through to\nmachine_check_expection() in traps.c, which calls die(), which OOPSes\nand sends SIGBUS to the process. This sometimes allows us to stumble\nonwards. For example we've seen UEs kill the kernel eehd and\nkhugepaged. However, the process killed could have held a lock, or it\ncould have been a more important process, etc: we can no longer make\nany assertions about the state of the machine. Similarly if we see a\nUE in skiboot (and again we've seen this happen), we're not in a\nposition where we can make any assertions about the state of the\nmachine.\n\nLikewise, for unknown or unrecognised errors, we're not able to say\nanything about the state of the machine.\n\nTherefore, if we have an unrecovered MCE, the most appropriate thing\nto do is to panic.\n\nThe second reason is that since e784b6499d9c (\"powerpc/powernv: Invoke\nopal_cec_reboot2() on unrecoverable machine check errors.\"), we\nattempt a special OPAL reboot on an unhandled MCE. This is so the\nhardware can record error data for later debugging.\n\nThe comments in that commit assert that we are heading down the panic\npath anyway. At the moment this is not always true. With UEs in kernel\nspace, for instance, they are marked as recoverable by the hardware,\nso if the attempt to reboot failed (e.g. old Skiboot), we wouldn't\npanic() but would simply die() and OOPS. It doesn't make sense to be\nstaggering on if we've just tried to reboot: we should panic().\n\nExplicitly panic() on unrecovered MCEs on PowerNV.\nUpdate the comments appropriately.\n\nThis fixes some hangs following EEH events on cxlflash setups.\n\nSigned-off-by: Daniel Axtens <dja@axtens.net>\nReviewed-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>\nReviewed-by: Ian Munsie <imunsie@au1.ibm.com>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/f2dd80ecca5f06b46134f2bd811f046c503c756c"},{"sha":"e87d68dd61035b52f5a4b9d91051c98893dad61e","author":{"email":"f2295d84e358395675bc8031be58672073ae065e@redhat.com","name":"Dave Airlie"},"message":"Merge branch 'drm-fixes-4.3' of git://people.freedesktop.org/~agd5f/linux into drm-fixes\n\nradeon and amdgpu fixes for 4.3. Highlights:\n- Move pm sysfs setup later in the driver init process to avoid\n  problems with laptop scripts attempting to change pm settings\n  before the driver has finished setting up the pm hardware.\n- Fix console restore if a drm app (e.g. X) is forcibly killed\n- Flag iceland support as experimental for now\n- Misc bug fixes\n\n* 'drm-fixes-4.3' of git://people.freedesktop.org/~agd5f/linux:\n  drm/amdgpu: fix memory leak in amdgpu_vm_update_page_directory\n  drm/amdgpu: fix 32-bit compiler warning\n  drm/amdgpu: flag iceland as experimental\n  drm/amdgpu: check before checking pci bridge registers\n  drm/amdgpu: fix num_crtc on CZ\n  drm/amdgpu: restore the fbdev mode in lastclose\n  drm/radeon: restore the fbdev mode in lastclose\n  drm/radeon: add quirk for ASUS R7 370\n  drm/amdgpu: add pm sysfs files late\n  drm/radeon: add pm sysfs files late","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/e87d68dd61035b52f5a4b9d91051c98893dad61e"},{"sha":"621bd0f6982badd6483acb191eb7b6226a578328","author":{"email":"c1b6782c4af8f0673da8923a0702a1832e5940f4@ffwll.ch","name":"Daniel Vetter"},"message":"drm: Fix locking for sysfs dpms file\n\nWith atomic drivers we need to make sure that (at least in general)\nproperty reads hold the right locks. But the legacy dpms property is\nspecial and can be read locklessly. Since userspace loves to just\nrandomly look at that all the time (like with \"status\") do that.\n\nTo make it clear that we play tricks use the READ_ONCE compiler\nbarrier (and also for paranoia).\n\nNote that there's not really anything bad going on since even with the\nnew atomic paths we eventually end up not chasing any pointers (and\nhence possibly freed memory and other fun stuff). The locking WARNING\nhas been added in\n\ncommit 88a48e297b3a3bac6022c03babfb038f1a886cea\nAuthor: Rob Clark <robdclark@gmail.com>\nDate:   Thu Dec 18 16:01:50 2014 -0500\n\n    drm: add atomic properties\n\nbut since drivers are converting not everyone will have seen this from\nthe start.\n\nJens reported this and submitted a patch to just grab the\nmode_config.connection_mutex, but we can do a bit better.\n\nv2: Remove unused variables I failed to git add for real.\n\nReference: http://mid.gmane.org/20150928194822.GA3930@kernel.dk\nReported-by: Jens Axboe <axboe@fb.com>\nTested-by: Jens Axboe <axboe@fb.com>\nCc: Rob Clark <robdclark@gmail.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Daniel Vetter <daniel.vetter@intel.com>\nSigned-off-by: Dave Airlie <airlied@redhat.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/621bd0f6982badd6483acb191eb7b6226a578328"},{"sha":"39b91b8144e028cbe383548f76c1f8cdb7977532","author":{"email":"461e4c5d78af46271bfe0c565bd09a6cb76dfcc4@qti.qualcomm.com","name":"Maharaja Kennadyrajan"},"message":"ath10k: increase pci wakeup timeout to 30 ms\n\nIt is noticed that pci wakeup time is exceeding current timeout (10ms)\nrandomly which is tested on QCA988x. So, the wake up time is increased\nto 30 ms and added debug prints to log total timeout.\n\nSigned-off-by: Maharaja Kennadyrajan <c_mkenna@qti.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/39b91b8144e028cbe383548f76c1f8cdb7977532"},{"sha":"ab4e3db043589204041c00272f751d05b4e52c50","author":{"email":"58b9aefd02b38fd9636344325c091015d8dc872b@qti.qualcomm.com","name":"Rajkumar Manoharan"},"message":"ath10k: optimize ce_lock on post rx buffer processing\n\nAfter processing received packets from copy engine, host will allocate\nnew buffer and queue them back to copy engine ring for further\npacket reception. On post rx processing path, skb allocation and\ndma mapping are unnecessarily handled within ce_lock. This is affecting\npeak throughput and also causing more CPU consumption. Optimize this\nby acquiring ce_lock only when accessing copy engine ring and moving\nskb allocation out of ce_lock.\n\nIn AP148 platform with QCA99x0 in conducted environment, UDP uplink peak\nthroughput is improved from ~1320 Mbps to ~1450 Mbps and TCP uplink peak\nthroughput is increased from ~1240 Mbps (70% host CPU load) to ~1300 Mbps\n(71% CPU load). Similarly ~40Mbps improvement is observed in downlink\npath.\n\nSigned-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/ab4e3db043589204041c00272f751d05b4e52c50"},{"sha":"72f8cef5d1155209561b01e092ce1a04ad50c4cb","author":{"email":"d7e27a4e12eef187ad6424baaf2437ac27664ca4@qti.qualcomm.com","name":"Vivek Natarajan"},"message":"ath10k: use station's current operating mode from assoc request\n\nThe current number of spatial streams used by the client is advertised\nas a separate IE in assoc request. Use this information to set\nthe NSS operating mode.\n\nFixes: 45c9abc059fa (\"ath10k: implement more versatile set_bitrate_mask\").\nSigned-off-by: Vivek Natarajan <nataraja@qti.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/72f8cef5d1155209561b01e092ce1a04ad50c4cb"},{"sha":"5a813da0068dbe46b77897c955b4059c7ffee4d8","author":{"email":"986e0823f9b2d50b670bb5c00ecae3f822b2e2ad@QCA.qualcomm.com","name":"Vladimir Kondratiev"},"message":"wil6210: fix warning in system power management code\n\nFix compilation warning where CONFIG_PM defined while\nCONFIG_PM_SLEEP is not defined\n\nReport follows:\n\ntree:   git://github.com/kvalo/ath pending\nhead:   941145fc5e5afbb120271e5dfaf37213ddb55807\ncommit: df596be39294d9712e5d568063a48448031e0a9f [37/39] wil6210: system power management\nconfig: xtensa-allyesconfig (attached as .config)\nreproduce:\n  wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross\n  chmod +x ~/bin/make.cross\n  git checkout df596be39294d9712e5d568063a48448031e0a9f\n  # save the attached .config to linux build tree\n  make.cross ARCH=xtensa\n\nAll warnings (new ones prefixed by >>):\n\n>> drivers/net/wireless/ath/wil6210/pcie_bus.c:264:12: warning: 'wil6210_suspend' defined but not used [-Wunused-function]\n    static int wil6210_suspend(struct device *dev, bool is_runtime)\n               ^\n>> drivers/net/wireless/ath/wil6210/pcie_bus.c:291:12: warning: 'wil6210_resume' defined but not used [-Wunused-function]\n    static int wil6210_resume(struct device *dev, bool is_runtime)\n               ^\nReported-by: kbuild test robot <fengguang.wu@intel.com>\nSigned-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/5a813da0068dbe46b77897c955b4059c7ffee4d8"},{"sha":"3b282bc6095f77908cb83427d93f0764e8419fdb","author":{"email":"986e0823f9b2d50b670bb5c00ecae3f822b2e2ad@QCA.qualcomm.com","name":"Vladimir Kondratiev"},"message":"wil6210: Add proper handling for invalid frames on Rx\n\nOn Rx, when invalid frame is received and dropped,\nreaping of next frames from Rx ring is stopped.\n\nThis stops NAPI polling and re-enables the Rx interrupt.\n\nHowever, in cases where no more frames received,\ninterrupt will not be triggered and rest of Rx frames\nwill not be processed.\n\nSkip bad frames and continue to reap Rx packets when\nsuch frames are encountered, and add statistics for\nsuch frames for debug.\n\nSigned-off-by: Hamad Kadmany <qca_hkadmany@qca.qualcomm.com>\nSigned-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/3b282bc6095f77908cb83427d93f0764e8419fdb"},{"sha":"bf2f67343eedc276b8441f91d8daaef4f3ed11d0","author":{"email":"986e0823f9b2d50b670bb5c00ecae3f822b2e2ad@QCA.qualcomm.com","name":"Vladimir Kondratiev"},"message":"wil6210: log firmware crash information\n\nPrint firmware and ucode assert codes when firmware crashed.\n\nSigned-off-by: Lior David <liord@qti.qualcomm.com>\nSigned-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/bf2f67343eedc276b8441f91d8daaef4f3ed11d0"},{"sha":"6cc6c468381e369e6450257645cf65c67f9f4a1b","author":{"email":"dc0aab724493729074b788f7042203d95fcf7d97@QCA.qualcomm.com","name":"Vladimir Shulman"},"message":"wil6210: pmc logger bug fix\n\nWhen allocating pmc descriptor, the structure is\ninitially created on stack and later copied to\nthe physical ring (device) memory. The descriptor\nstructure must be initialized to zero to avoid\ngarbage configuration, which may result in pmc\nmechanism malfunctioning.\n\nSigned-off-by: Vladimir Shulman <QCA_shulmanv@QCA.qualcomm.com>\nSigned-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/6cc6c468381e369e6450257645cf65c67f9f4a1b"},{"sha":"68682b4108f1254a34e40f516f9ab1f49b4754fc","author":{"email":"986e0823f9b2d50b670bb5c00ecae3f822b2e2ad@QCA.qualcomm.com","name":"Vladimir Kondratiev"},"message":"wil6210: treat broadcast bssid as \"disconnect all\"\n\nHostapd request disconnect for broadcast bssid when it\nwants to disconnect all stations from the AP.\n\nDetect this and really disconnect all connected stations.\n\nSigned-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/68682b4108f1254a34e40f516f9ab1f49b4754fc"},{"sha":"a8313341c4a83d5da18aad07501119da649d58dc","author":{"email":"986e0823f9b2d50b670bb5c00ecae3f822b2e2ad@QCA.qualcomm.com","name":"Vladimir Kondratiev"},"message":"wil6210: support BAR (BlockAck Req)\n\nBAR frames delivered to the host via Rx path; whole BAR frame\nget delivered. Advance sequence in the reorder buffer and release\nold frames, as per IEEE802.11 spec.\n\nFirmware will reply to BAR, driver responsibility is only reorder\nbuffer management.\n\nSigned-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.14/commits/a8313341c4a83d5da18aad07501119da649d58dc"}]}