linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4 1/3] nl80211: Add support for beacon tx mode
Date: Tue, 10 Aug 2021 14:02:36 +0530	[thread overview]
Message-ID: <0430f508f293d0b5b0d82cc1da78284d@codeaurora.org> (raw)
In-Reply-To: <0e3d0abd-a895-77d8-d3a6-ef6d2616b7db@nbd.name>

On 2021-06-29 23:14, Felix Fietkau wrote:
> On 2021-06-23 13:16, Johannes Berg wrote:
>> First, I'd like to see some input from other vendors - is this useful?
>> 
>> I have no objections to it and it comes with an in-kernel driver, so 
>> I'm
>> inclined to accept it, but maybe we should have other modes, etc.?
> I haven't seen any config option like this outside of QCA stuff.
> It seems to me that before getting merged, the documentation should at
> least cover when and why the *user* would configure this implementation
> detail, instead of having the driver/fw make a reasonable decision on
> its own.
> 
> - Felix
[Maha]: I will do the documentation for this in the next version 
patchset.

  reply	other threads:[~2021-08-10  8:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 15:07 [PATCH v4 0/3] Add support to configure beacon tx mode Maharaja Kennadyrajan
2021-06-08 15:07 ` [PATCH v4 1/3] nl80211: Add support for " Maharaja Kennadyrajan
2021-06-23 11:16   ` Johannes Berg
2021-06-29 17:44     ` Felix Fietkau
2021-08-10  8:32       ` Maharaja Kennadyrajan [this message]
2021-08-10  8:31     ` Maharaja Kennadyrajan
2021-06-08 15:07 ` [PATCH v4 2/3] mac80211: " Maharaja Kennadyrajan
2021-06-08 15:07 ` [PATCH v4 3/3] ath11k: " Maharaja Kennadyrajan
2021-06-08 21:41 ` [PATCH v4 0/3] Add support to configure " Jeff Johnson

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=0430f508f293d0b5b0d82cc1da78284d@codeaurora.org \
    --to=mkenna@codeaurora.org \
    --cc=ath11k@lists.infradead.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 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).