Kalle Valo <kv...@codeaurora.org> writes: > Andrew Lutomirski <l...@kernel.org> wrote: >> Eric Biggers pointed out that the orinoco driver pointed scatterlists >> at the stack. >> >> Fix it by switching from ahash to shash. The result should be >> simpler, faster, and more correct. >> >> Cc: sta...@vger.kernel.org # 4.9 only >> Reported-by: Eric Biggers <ebigge...@gmail.com> >> Signed-off-by: Andy Lutomirski <l...@kernel.org> > > 11 patches applied to wireless-drivers-next.git, thanks. > > 1fef293b8a98 orinoco: Use shash instead of ahash for MIC calculations > a08b98196a36 rt2800: make rx ampdu_factor depend on number of rx chains > e49abb19d1bf rt2800: don't set ht parameters for non-aggregated frames > a51b89698ccc rt2800: set minimum MPDU and PSDU lengths to sane values > 8f03a7c6e7f9 rt2800: set MAX_PSDU len according to remote STAs capabilities > 8845254112ac rt2800: rename adjust_freq_offset function > bc0077053948 rt2800: warn if doing VCO recalibration for unknow RF chip > 24d42ef3b152 rt2800: perform VCO recalibration for RF5592 chip > d96324703ffa rt2x00: merge agc and vco works with link tuner > eb79a8fe94c8 rt2800: replace mdelay by usleep on vco calibration. > 31369c323ba0 rt2800: replace msleep() with usleep_range() on channel switch
Oh man, when I was applying rt2800 patches I did an off by one error with my patchwork script ('commit 2-12' vs 'commit 1-11') and accidentally applied this orinoco patch to wireless-drivers-next along with the 10 rt2800 patches above. And failed to spot that before pushing the tree :( As this orinoco patch is pretty important I'll cherry pick it manually to wireless-drivers also so that it goes to 4.10. This means that the patch is in both trees, but just with a different commit id. Sorry for the mess. -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html