From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev <netdev@vger.kernel.org>, linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211-next next-2020-02-24
Date: Mon, 24 Feb 2020 20:33:12 +0100 [thread overview]
Message-ID: <BCCC37CB-FA6D-433C-B772-EC46EF734FED@holtmann.org> (raw)
In-Reply-To: <20200224183442.82066-1-johannes@sipsolutions.net>
Hi Johannes,
> Some new updates - initial beacon protection support and TID
> configuration are the interesting parts, but need drivers to
> fill in, so that'll come from Kalle later :)
>
> Please pull and let me know if there's any problem.
>
> Thanks,
> johannes
>
>
>
> The following changes since commit 92df9f8a745ee9b8cc250514272345cb2e74e7ef:
>
> Merge branch 'mvneta-xdp-ethtool-stats' (2020-02-16 20:04:42 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git tags/mac80211-next-for-net-next-2020-02-24
>
> for you to fetch changes up to 370f51d5edac83bfdb9a078d7098f06403dfa4bc:
>
> mac80211: Add api to support configuring TID specific configuration (2020-02-24 14:07:01 +0100)
>
> ----------------------------------------------------------------
> A new set of changes:
> * lots of small documentation fixes, from Jérôme Pouiller
> * beacon protection (BIGTK) support from Jouni Malinen
> * some initial code for TID configuration, from Tamizh chelvam
> * I reverted some new API before it's actually used, because
> it's wrong to mix controlled port and preauth
> * a few other cleanups/fixes
>
> ----------------------------------------------------------------
> Amol Grover (1):
> cfg80211: Pass lockdep expression to RCU lists
>
> Emmanuel Grumbach (1):
> cfg80211: remove support for adjacent channel compensation
>
> Johannes Berg (4):
> mac80211: check vif pointer before airtime calculation
> Revert "mac80211: support NL80211_EXT_FEATURE_CONTROL_PORT_OVER_NL80211_MAC_ADDRS"
> Revert "nl80211: add src and dst addr attributes for control port tx/rx"
so I am bit concerned if these reverts are pushed so quickly without allowing ample time to discuss or review them on the mailing list. I for one, don’t agree with the assessment made to justify these reverts.
Regards
Marcel
next prev parent reply other threads:[~2020-02-24 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 18:34 pull-request: mac80211-next next-2020-02-24 Johannes Berg
2020-02-24 19:33 ` Marcel Holtmann [this message]
2020-02-24 19:34 ` Johannes Berg
2020-02-24 23:42 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BCCC37CB-FA6D-433C-B772-EC46EF734FED@holtmann.org \
--to=marcel@holtmann.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox