The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: feng.wei8@zte.com.cn, linux-kernel@vger.kernel.org,
	tang.dongxing@zte.com.cn, feng.wei8@zte.com.cn,
	shao.mingyin@zte.com.cn, xie.ludan@zte.com.cn,
	yang.guang5@zte.com.cn, yang.yang29@zte.com.cn,
	ye.xingchen@zte.com.cn, xu.xin16@zte.com.cn
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: minstrel_ht: Replace nested min() with single min3()
Date: Mon, 17 Mar 2025 09:30:30 +0100	[thread overview]
Message-ID: <f6dfffc0-a9bd-4a5f-9d83-f3a4b7918010@kernel.org> (raw)
In-Reply-To: <20250315111254625RMIKeUh51j1Xk9CWuu2LT@zte.com.cn>

On 15/03/2025 04:12, feng.wei8@zte.com.cn wrote:
> From: FengWei <feng.wei8@zte.com.cn>
> 
> Use min3() macro instead of nesting min() to simplify the return
> statement.
> 
> Signed-off-by: FengWei <feng.wei8@zte.com.cn>
> ---
>  net/mac80211/rc80211_minstrel_ht.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/net/mac80211/rc80211_minstrel_ht.c b/net/mac80211/rc80211_minstrel_ht.c
> index 08f3f530f984..31a3b6e4c58d 100644
> --- a/net/mac80211/rc80211_minstrel_ht.c
> +++ b/net/mac80211/rc80211_minstrel_ht.c
> @@ -1010,7 +1010,7 @@ minstrel_ht_refill_sample_rates(struct minstrel_ht_sta *mi)
>  	u32 prob_dur = minstrel_get_duration(mi->max_prob_rate);
>  	u32 tp_dur = minstrel_get_duration(mi->max_tp_rate[0]);
>  	u32 tp2_dur = minstrel_get_duration(mi->max_tp_rate[1]);
> -	u32 fast_rate_dur = min(tp_dur, tp2_dur, prob_dur);
> +	u32 fast_rate_dur = min3(tp_dur, tp2_dur, prob_dur);

This is automation-generated junk code. How does it "simplify the
statement"?

Can ZTE slow down this flood of automation or research experiment on
kernel community?

Best regards,
Krzysztof

  parent reply	other threads:[~2025-03-17  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-15  3:12 [PATCH] mac80211: minstrel_ht: Replace nested min() with single min3() feng.wei8
2025-03-16 14:00 ` Johannes Berg
2025-03-17  4:55   ` feng.wei8
2025-03-17  8:27     ` Krzysztof Kozlowski
2025-03-17  8:30 ` Krzysztof Kozlowski [this message]
2025-03-17  8:31   ` 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=f6dfffc0-a9bd-4a5f-9d83-f3a4b7918010@kernel.org \
    --to=krzk@kernel.org \
    --cc=feng.wei8@zte.com.cn \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shao.mingyin@zte.com.cn \
    --cc=tang.dongxing@zte.com.cn \
    --cc=xie.ludan@zte.com.cn \
    --cc=xu.xin16@zte.com.cn \
    --cc=yang.guang5@zte.com.cn \
    --cc=yang.yang29@zte.com.cn \
    --cc=ye.xingchen@zte.com.cn \
    /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