From: Johannes Berg <johannes@sipsolutions.net>
To: "Sriram R (QUIC)" <quic_srirrama@quicinc.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC v2] mac80211: prepare sta handling for MLO support
Date: Mon, 04 Apr 2022 17:51:19 +0200 [thread overview]
Message-ID: <1524068599dffb64456ce5032a0cce834ef2f21f.camel@sipsolutions.net> (raw)
In-Reply-To: <SN6PR02MB43347C8B21DA6B7F3D6F0A92F7E59@SN6PR02MB4334.namprd02.prod.outlook.com>
On Mon, 2022-04-04 at 15:50 +0000, Sriram R (QUIC) wrote:
> > > Hi Johannes,
> > > >
> > > > I think this looks fine - want to send it as a PATCH? I think
> > > > I'll
> > > > just apply the spatch directly.
> > > Sure, Let me send out a PATCH shortly.
> > > >
> > > > If there's any needed fixups beyond the spatch that might be
> > > > good to know
> > too.
> > > So, in this patch (mac80211) I had to manually fix couple of
> > > changes around
> > ADD_STA_STATS, TRACE_EVENT macros.
> > >
> > > In drivers, only below change was required in addition.
> > >
> >
> > Nice! So if you include all the manual bits, you can also leave out
> > mac80211 changes from the spatch if you like, I'll just run the
> > spatch when
> > applying it so we have it on the exact tree snapshot.
> I just sent out the patch version, I'll send v2 with only the manual
> mac80211 changes, so running the spatch on top should help compile
> seamlessly.
You know what, it doesn't matter. I can put the pieces together, no
worries.
johannes
prev parent reply other threads:[~2022-04-04 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 11:59 [RFC v2] mac80211: prepare sta handling for MLO support Sriram R
2022-04-04 13:22 ` Johannes Berg
2022-04-04 15:40 ` Sriram R (QUIC)
2022-04-04 15:41 ` Johannes Berg
2022-04-04 15:50 ` Sriram R (QUIC)
2022-04-04 15:51 ` Johannes Berg [this message]
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=1524068599dffb64456ce5032a0cce834ef2f21f.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_srirrama@quicinc.com \
/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