Johannes Berg <[email protected]> writes: > On Wed, 2019-02-06 at 20:11 +0200, Kalle Valo wrote: >> Luca Coelho <[email protected]> writes: >> >> > From: Johannes Berg <[email protected]> >> > >> > Expose the trigger-based PPDU SIG-A bandwidth to radiotap in >> > the newly defined bits thereof. >> > >> > Signed-off-by: Johannes Berg <[email protected]> >> > Signed-off-by: Luca Coelho <[email protected]> >> >> [...] >> >> > --- a/include/net/ieee80211_radiotap.h >> > +++ b/include/net/ieee80211_radiotap.h >> > @@ -291,6 +291,12 @@ enum ieee80211_radiotap_he_bits { >> > >> > IEEE80211_RADIOTAP_HE_DATA6_NSTS = 0x000f, >> > IEEE80211_RADIOTAP_HE_DATA6_DOPPLER = 0x0010, >> > + IEEE80211_RADIOTAP_HE_DATA6_TB_PPDU_BW_KNOWN = 0x0020, >> > + IEEE80211_RADIOTAP_HE_DATA6_TB_PPDU_BW = 0x00c0, >> > + IEEE80211_RADIOTAP_HE_DATA6_TB_PPDU_BW_20MHZ = 0, >> > + IEEE80211_RADIOTAP_HE_DATA6_TB_PPDU_BW_40MHZ = 1, >> > + IEEE80211_RADIOTAP_HE_DATA6_TB_PPDU_BW_80MHZ = 2, >> > + IEEE80211_RADIOTAP_HE_DATA6_TB_PPDU_BW_160MHZ = 3, >> > IEEE80211_RADIOTAP_HE_DATA6_TXOP = 0x7f00, >> > IEEE80211_RADIOTAP_HE_DATA6_MIDAMBLE_PDCTY = 0x8000, >> > }; >> >> Johannes, as you wrote the patch I take it that you are ok to push this >> via wireless-drivers-next? > > Oops, maybe I should've split that, but it doesn't really matter much.
IMHO splitting does not make any sense, we had four changes to ieee80211_radiotap.h last year so the chance of conflicts is low :) Just wanted to make sure you are ok with this. > Sure, take it. Great, thanks. I'll pull this now. -- Kalle Valo
