From: "Muna Sinada" <msinada@codeaurora.org>
To: "'Johannes Berg'" <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH 2/2] mac80211: Handling driver updated MU-EDCA params
Date: Wed, 11 Aug 2021 23:41:50 -0700 [thread overview]
Message-ID: <000001d78f45$2234ccc0$669e6640$@codeaurora.org> (raw)
In-Reply-To: <d94af0309a1c7a1dee1841580b5938898426a10b.camel@sipsolutions.net>
Hello Johannes,
Please drop this patch.
Thank you,
Muna
-----Original Message-----
From: Johannes Berg <johannes@sipsolutions.net>
Sent: Wednesday, August 11, 2021 3:07 AM
To: Muna Sinada <msinada@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: Handling driver updated MU-EDCA params
On Tue, 2021-08-10 at 19:48 -0700, Muna Sinada wrote:
> Hello Johannes,
>
> I saw on your review comment that this wrapper is not needed. I wanted
> to confirm with you if it would be ok to call a cfg80211 API from a
> mac80211 based driver, since that is what would be done if this
> wrapper is removed.
Yes, that's fine.
> Additionally, another reason I have this wrapper is so I can place a
> tracepoint. What are your thoughts about this?
You already have a tracepoint on cfg80211, seems sufficient?
johannes
next prev parent reply other threads:[~2021-08-12 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 22:54 [PATCH 1/2] cfg80211: Handling driver updated MU-EDCA params Muna Sinada
2020-12-08 22:54 ` [PATCH 2/2] mac80211: " Muna Sinada
2021-02-12 8:48 ` Johannes Berg
2021-08-11 2:48 ` Muna Sinada
2021-08-11 10:07 ` Johannes Berg
2021-08-12 6:41 ` Muna Sinada [this message]
2021-02-12 8:48 ` [PATCH 1/2] cfg80211: " 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='000001d78f45$2234ccc0$669e6640$@codeaurora.org' \
--to=msinada@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).