All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: 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:01:37 +0530	[thread overview]
Message-ID: <65b594ccab0a30bfb5bc2122cbf73f20@codeaurora.org> (raw)
In-Reply-To: <f14e6e6b81978ace4580774981a7e032b4001182.camel@sipsolutions.net>

On 2021-06-23 16:46, 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.?
> 
> 
>> + * @NL80211_ATTR_BEACON_TX_MODE: used to configure the beacon tx mode 
>> as
>> + *      staggered mode = 1 or burst mode = 2 in %NL80211_CMD_START_AP 
>> or
>> + *      %NL80211_CMD_JOIN_MESH from user-space.
> 
[Maha]: will replace the hard-coded values with enum here.
> 
> This should refer to the enum, not the hard-coded constants.
>> 
>> +/**
>> + * enum nl80211_beacon_tx_mode - Beacon Tx Mode enum.
>> + *      Used to configure beacon staggered mode or beacon burst mode.
>> + */
>> +enum nl80211_beacon_tx_mode {
> 
> 
> That's missing kernel-doc, and you also don't specify what default
> means. Why is it even here?
> 
[Maha]: sure, I will add the same in the kernel-doc.
>> +	[NL80211_ATTR_BEACON_TX_MODE] = NLA_POLICY_RANGE(NLA_U32, 1,
> 2),
> 
> That really also needs to use the enum, not hard-coded constants...
[Maha]: will replace the hard-coded values with enum also here.
> 
> johannes

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: 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:01:37 +0530	[thread overview]
Message-ID: <65b594ccab0a30bfb5bc2122cbf73f20@codeaurora.org> (raw)
In-Reply-To: <f14e6e6b81978ace4580774981a7e032b4001182.camel@sipsolutions.net>

On 2021-06-23 16:46, 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.?
> 
> 
>> + * @NL80211_ATTR_BEACON_TX_MODE: used to configure the beacon tx mode 
>> as
>> + *      staggered mode = 1 or burst mode = 2 in %NL80211_CMD_START_AP 
>> or
>> + *      %NL80211_CMD_JOIN_MESH from user-space.
> 
[Maha]: will replace the hard-coded values with enum here.
> 
> This should refer to the enum, not the hard-coded constants.
>> 
>> +/**
>> + * enum nl80211_beacon_tx_mode - Beacon Tx Mode enum.
>> + *      Used to configure beacon staggered mode or beacon burst mode.
>> + */
>> +enum nl80211_beacon_tx_mode {
> 
> 
> That's missing kernel-doc, and you also don't specify what default
> means. Why is it even here?
> 
[Maha]: sure, I will add the same in the kernel-doc.
>> +	[NL80211_ATTR_BEACON_TX_MODE] = NLA_POLICY_RANGE(NLA_U32, 1,
> 2),
> 
> That really also needs to use the enum, not hard-coded constants...
[Maha]: will replace the hard-coded values with enum also here.
> 
> johannes

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

Thread overview: 18+ 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 ` Maharaja Kennadyrajan
2021-06-08 15:07 ` [PATCH v4 1/3] nl80211: Add support for " Maharaja Kennadyrajan
2021-06-08 15:07   ` Maharaja Kennadyrajan
2021-06-23 11:16   ` Johannes Berg
2021-06-23 11:16     ` Johannes Berg
2021-06-29 17:44     ` Felix Fietkau
2021-06-29 17:44       ` Felix Fietkau
2021-08-10  8:32       ` Maharaja Kennadyrajan
2021-08-10  8:32         ` Maharaja Kennadyrajan
2021-08-10  8:31     ` 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   ` Maharaja Kennadyrajan
2021-06-08 15:07 ` [PATCH v4 3/3] ath11k: " Maharaja Kennadyrajan
2021-06-08 15:07   ` Maharaja Kennadyrajan
2021-06-08 21:41 ` [PATCH v4 0/3] Add support to configure " Jeff Johnson
2021-06-08 21:41   ` 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=65b594ccab0a30bfb5bc2122cbf73f20@codeaurora.org \
    --to=mkenna@codeaurora.org \
    --cc=ath11k@lists.infradead.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 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.