From: <murugana@codeaurora.org>
To: "'Johannes Berg'" <johannes@sipsolutions.net>,
<linux-wireless@vger.kernel.org>
Cc: "'Felix Fietkau'" <nbd@nbd.name>
Subject: RE: [PATCH] mac80211: WFA Multi-AP backhaul STA Rx requirement
Date: Tue, 28 Aug 2018 17:22:56 +0530 [thread overview]
Message-ID: <003d01d43ec5$ab42fb00$01c8f100$@codeaurora.org> (raw)
In-Reply-To: <1535450281.5895.34.camel@sipsolutions.net>
Hi Johannes,
> Hmm. The subject/patch title isn't very clear - does it *implement* =
this
> requirement? Or do something else with it? Please clarify.
>=20
Yes, this patch implements the missing Rx requirement (ii) for backhaul =
STA
below.
..
> > Receiver requirements
> > ---------------------
> > 1. Fronthaul AP
> > i) When SA!=3DTA of backhaul STA, must support receiving =
4-address
> > format frames
> > ii) When SA=3D=3DTA of backhaul STA, must support receiving =
both
> > 3-address and 4-address format frames
> >
> > (mac80211 support both 3-addr & 4-addr via AP/VLAN
> > interface)
> >
> > 2. Backhaul STA
> > i) When DA!=3DRA of backhaul STA, must support receiving =
4-address
> > format frames
> > ii) When DA=3D=3DRA of backhaul STA, must support receiving =
both
> > 3-address and 4-address format frames
> >
> > (mac80211 support only receiving 4-address format via
> > use_4addr)
> >
> > This patch addresses the above Rx requirement (ii) for backhaul STA.
This patch implements the Rx requirement (ii) of receiving unicast =
3-addr frames in
addition to 4-addr format frames.
Thanks,
Sathishkumar
next prev parent reply other threads:[~2018-08-28 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 12:47 [PATCH] mac80211: WFA Multi-AP backhaul STA Rx requirement Sathishkumar Muruganandam
2018-08-28 9:58 ` Johannes Berg
2018-08-28 11:52 ` murugana [this message]
2018-08-28 11:55 ` Johannes Berg
2018-08-28 12:24 ` Sathishkumar Muruganandam
2018-08-28 11:53 ` 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='003d01d43ec5$ab42fb00$01c8f100$@codeaurora.org' \
--to=murugana@codeaurora.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.