From: Johannes Berg <johannes@sipsolutions.net>
To: Balaji Pothunoori <bpothuno@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 1/2] cfg80211: last ack signal support in station dump
Date: Fri, 15 Jun 2018 13:41:13 +0200 [thread overview]
Message-ID: <1529062873.10037.9.camel@sipsolutions.net> (raw)
In-Reply-To: <1528121469-16450-2-git-send-email-bpothuno@codeaurora.org>
On Mon, 2018-06-04 at 19:41 +0530, Balaji Pothunoori wrote:
>
> +++ b/include/uapi/linux/nl80211.h
> @@ -3000,8 +3000,8 @@ enum nl80211_sta_bss_param {
> * received from the station (u64, usec)
> * @NL80211_STA_INFO_PAD: attribute used for padding for 64-bit alignment
> * @NL80211_STA_INFO_ACK_SIGNAL: signal strength of the last ACK frame(u8, dBm)
> - * @NL80211_STA_INFO_DATA_ACK_SIGNAL_AVG: avg signal strength of (data)
> - * ACK frame (s8, dBm)
> + * @NL80211_STA_INFO_ACK_SIGNAL_AVG: avg signal strength of data or management
> + * ACK frames(s8, dBm)
> * @__NL80211_STA_INFO_AFTER_LAST: internal
> * @NL80211_STA_INFO_MAX: highest possible station info attribute
> */
> @@ -3041,7 +3041,7 @@ enum nl80211_sta_info {
> NL80211_STA_INFO_RX_DURATION,
> NL80211_STA_INFO_PAD,
> NL80211_STA_INFO_ACK_SIGNAL,
> - NL80211_STA_INFO_DATA_ACK_SIGNAL_AVG,
> + NL80211_STA_INFO_ACK_SIGNAL_AVG,
Wait, what happened here? You can't remove old API.
> @@ -5128,9 +5128,9 @@ enum nl80211_feature_flags {
> * "radar detected" event.
> * @NL80211_EXT_FEATURE_CONTROL_PORT_OVER_NL80211: Driver supports sending and
> * receiving control port frames over nl80211 instead of the netdevice.
> - * @NL80211_EXT_FEATURE_DATA_ACK_SIGNAL_SUPPORT: This Driver support data ack
> - * rssi if firmware support, this flag is to intimate about ack rssi
> - * support to nl80211.
> + * @NL80211_EXT_FEATURE_ACK_SIGNAL_SUPPORT: This Driver support ack rssi if
> + * firmware support, this flag is to intimate about ack rssi support
> + * to nl80211.
Same here, why are you removing the data-ack-signal API?
Is that just a rebase error or something?
Or is it intentional, but then please explain what you're trying to do
and I can help find a correct solutions.
johannes
next prev parent reply other threads:[~2018-06-15 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 14:11 [PATCH v2 0/2] cfg80211/mac80211: last ack signal support in station dump Balaji Pothunoori
2018-06-04 14:11 ` [PATCH v2 1/2] cfg80211: " Balaji Pothunoori
2018-06-15 11:41 ` Johannes Berg [this message]
2018-06-18 9:18 ` Balaji Pothunoori
2018-06-18 20:51 ` Johannes Berg
2018-06-04 14:11 ` [PATCH v2 2/2] mac80211: " Balaji Pothunoori
2018-06-15 11:43 ` Johannes Berg
2018-06-18 10:25 ` Balaji Pothunoori
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=1529062873.10037.9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=bpothuno@codeaurora.org \
--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).