Hi Kale, On Fri, 2018-01-12 at 13:31 +0200, Kalle Valo wrote: > From: Luca Coelho <luciano.coelho@xxxxxxxxx> > > > > Hi, > > > > Here's the fourth and probably last batch of patches intended for > > 4.16. Nothing major, just continued development, some cleanups and > > small fixes here and there. > > > > * Fix a UBSAN warning; > > * Improvement in the net-stack/driver log syncing > > * An RCU lock fix in the new rate-scaling code; > > * Small cleanups; > > > > As usual, I'm pushing this to a pending branch, for kbuild bot, and > > will send a pull-request later. > > > > FYI, I'll be on holidays/vacations for the next few weeks, so there > > will probably not be much activity in the iwlwifi driver code. > > > > Please review. > > > > Cheers, > > Luca. > > > > > > Luca Coelho (1): > > iwlwifi: mvm: check if mac80211_queue is valid in > > iwl_mvm_disable_txq > > > > Mordechay Goodstein (1): > > iwlwifi: set default timstamp marker cmd > > > > Sara Sharon (3): > > iwlwifi: mvm: flip AMSDU addresses only for 9000 family > > iwlwifi: mvm: take RCU lock before dereferencing > > iwlwifi: mvm: move TSO segment to a separate function > > Most likely the merge window starts in 9 days so I need to start > getting > patches ready. As Luca is away should I apply these patches directly > to > wireless-drivers-next? > First let me thank you for tracking this. I don't see anything that we really need in 4.16 here. Besides Luca's UBSAN warning, all the rest is for a new device family which won't be supported in 4.16 anyway. So I opt to wait for Luca here.
