From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@nbd.name>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3/4] mac80211: support fast-rx with incompatible PS capabilities when PS is disabled
Date: Fri, 23 Feb 2018 12:25:33 +0100 [thread overview]
Message-ID: <1519385133.2231.7.camel@sipsolutions.net> (raw)
In-Reply-To: <20180223090606.55726-3-nbd@nbd.name>
I've applied 1 to mac80211, and 2/3 to mac80211-next, so please only
resend 4, unless you can convince me it's OK as is :-)
johannes
next prev parent reply other threads:[~2018-02-23 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 9:06 [PATCH 1/4] mac80211: drop frames with unexpected DS bits from fast-rx to slow path Felix Fietkau
2018-02-23 9:06 ` [PATCH 2/4] mac80211: support AP 4-addr mode fast-rx Felix Fietkau
2018-02-23 9:06 ` [PATCH 3/4] mac80211: support fast-rx with incompatible PS capabilities when PS is disabled Felix Fietkau
2018-02-23 11:25 ` Johannes Berg [this message]
2018-02-23 9:06 ` [PATCH 4/4] mac80211: support station 4-addr mode fast-rx Felix Fietkau
2018-02-23 11:24 ` Johannes Berg
2018-02-23 12:54 ` Felix Fietkau
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=1519385133.2231.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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;
as well as URLs for NNTP newsgroup(s).