From: Johannes Berg <johannes@sipsolutions.net>
To: Yuan-Chi Pang <fu3mo6goo@gmail.com>
Cc: davem@davemloft.net, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mac80211: fix TX status reporting for ieee80211s
Date: Mon, 03 Sep 2018 10:33:30 +0200 [thread overview]
Message-ID: <1535963610.3437.10.camel@sipsolutions.net> (raw)
In-Reply-To: <1535699575-5672-1-git-send-email-fu3mo6goo@gmail.com> (sfid-20180831_091323_224304_305F21B4)
On Fri, 2018-08-31 at 15:12 +0800, Yuan-Chi Pang wrote:
> void ieee80211s_init(void);
> void ieee80211s_update_metric(struct ieee80211_local *local,
> - struct sta_info *sta, struct sk_buff *skb);
> + struct sta_info *sta, struct ieee80211_tx_status *st);
please keep things indented properly
> void ieee80211s_update_metric(struct ieee80211_local *local,
> - struct sta_info *sta, struct sk_buff *skb)
> + struct sta_info *sta, struct ieee80211_tx_status *st)
and maybe fix the indentation here while you're changing it
> {
> - struct ieee80211_tx_info *txinfo = IEEE80211_SKB_CB(skb);
> - struct ieee80211_hdr *hdr = (struct ieee80211_hdr *) skb->data;
> + struct ieee80211_tx_info *txinfo = st->info;
> int failed;
>
> - if (!ieee80211_is_data(hdr->frame_control))
> - return;
Why are you removing this condition? You didn't say anything about that.
I sort of see why (you no longer even have the skb/hdr), but you should
indicate why this is OK.
> rate_control_tx_status(local, sband, status);
> + if (ieee80211_vif_is_mesh(&sta->sdata->vif))
> + ieee80211s_update_metric(local, sta, status)
This is the only "real" change I guess, some more description about it
would be good.
I can sort of reverse engineer it from your commit log, but you should
be more explicit.
johannes
next prev parent reply other threads:[~2018-09-03 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 7:12 [PATCH] mac80211: fix TX status reporting for ieee80211s Yuan-Chi Pang
2018-09-03 8:33 ` Johannes Berg [this message]
2018-09-06 8:57 ` Yuan-Chi Pang
2018-09-06 9:45 ` Yuan-Chi Pang
2018-09-06 9:47 ` 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=1535963610.3437.10.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=fu3mo6goo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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