From: Johannes Berg <johannes@sipsolutions.net>
To: Stefan Lippers-Hollmann <s.l-h@gmx.de>
Cc: Tom Psyborg <pozega.tomislav@gmail.com>,
Manikanta Pubbisetty <mpubbise@codeaurora.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] {nl,mac}80211: allow 4addr AP operation on crypto controlled devices
Date: Mon, 17 Jun 2019 09:06:51 +0200 [thread overview]
Message-ID: <e13d86030df7a5222ee144d85bbeec400ed8fa07.camel@sipsolutions.net> (raw)
In-Reply-To: <20190617070747.562b9388@mir> (sfid-20190617_070759_741392_4A382985)
On Mon, 2019-06-17 at 07:07 +0200, Stefan Lippers-Hollmann wrote:
> Hi
>
> On 2019-06-12, Johannes Berg wrote:
> > On Thu, 2019-06-06 at 20:41 +0200, Tom Psyborg wrote:
> > >
> > > Applying this patch instead of v1 broke WDS operation between two
> > > Litebeam AC Gen2 devices:
> >
> > I'm confused, and not even sure which version I applied now.
> >
> > Manikanta, can you please check this and which version I have and which
> > changes I might need?
>
> I've tested (and left it running/ monitored) for two days without
> any problems between QCA9984 (ZyXEL nbg6817/ ipq8065, WDS-AP, affected
> before 33d915d9e8ce811d8958915ccd18d71a66c7c495 "{nl,mac}80211: allow
> 4addr AP operation on crypto controlled devices" went in) and AR9340
> (TP-Link TL-WDR3600/ AR9344, WDS-Client, not affected by this issue),
> both under current (~2 days old) OpenWrt master[1] (ipq806x/ ath79,
> respectively). This patch is working fine and fixes the previous
> problems with 4addr on ath10k (QCA9984).
"This patch" is v3 then, presumably? I just checked, and it looks like I
indeed applied v3.
So basically you're saying it works as affected, since you were
previously affected by the unavailability of 4addr interfaces on ath10k
hardware, which are now available, right?
Tom, I notice you're using a very old base kernel ("backports-4.19.32-
1") - are you sure you were even able to apply this patch correctly?
johannes
next prev parent reply other threads:[~2019-06-17 7:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 9:25 [PATCH v3] {nl,mac}80211: allow 4addr AP operation on crypto controlled devices Manikanta Pubbisetty
2019-05-14 8:38 ` Johannes Berg
2019-05-31 4:33 ` Manikanta Pubbisetty
2019-06-06 18:41 ` Tom Psyborg
2019-06-12 19:30 ` Johannes Berg
2019-06-14 17:45 ` Tom Psyborg
2019-06-14 18:43 ` Johannes Berg
2019-06-14 20:27 ` Tom Psyborg
2019-06-14 20:37 ` Johannes Berg
2019-06-17 5:07 ` Stefan Lippers-Hollmann
2019-06-17 7:06 ` Johannes Berg [this message]
2019-06-17 7:36 ` Stefan Lippers-Hollmann
2019-06-17 11:32 ` Tom Psyborg
2019-06-28 14:02 ` Johannes Berg
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=e13d86030df7a5222ee144d85bbeec400ed8fa07.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mpubbise@codeaurora.org \
--cc=pozega.tomislav@gmail.com \
--cc=s.l-h@gmx.de \
/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).