From: Kalle Valo <kvalo@kernel.org>
To: Guo Zhengkui <guozhengkui@vivo.com>
Cc: "Jiri Slaby" <jirislaby@kernel.org>,
"Nick Kossifidis" <mickflemm@gmail.com>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
linux-wireless@vger.kernel.org (open list:ATHEROS ATH5K WIRELESS
DRIVER), netdev@vger.kernel.org (open list:NETWORKING DRIVERS),
linux-kernel@vger.kernel.org (open list),
zhengkui_guo@outlook.com
Subject: Re: [PATCH linux-next] net: ath: fix minmax.cocci warnings
Date: Mon, 16 May 2022 20:04:21 +0300 [thread overview]
Message-ID: <874k1pxvca.fsf@kernel.org> (raw)
In-Reply-To: <20220516134057.72365-1-guozhengkui@vivo.com> (Guo Zhengkui's message of "Mon, 16 May 2022 21:40:57 +0800")
Guo Zhengkui <guozhengkui@vivo.com> writes:
> Fix the following coccicheck warnings:
>
> drivers/net/wireless/ath/ath5k/phy.c:3139:62-63: WARNING
> opportunity for min()
> drivers/net/wireless/ath/ath9k/dfs.c:249:28-30: WARNING
> opportunity for max()
>
> Signed-off-by: Guo Zhengkui <guozhengkui@vivo.com>
> ---
> drivers/net/wireless/ath/ath5k/phy.c | 2 +-
> drivers/net/wireless/ath/ath9k/dfs.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Please split this into two patches, one for ath5k and one for ath9k.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-05-16 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 13:40 [PATCH linux-next] net: ath: fix minmax.cocci warnings Guo Zhengkui
2022-05-16 17:04 ` Kalle Valo [this message]
2022-05-17 2:39 ` [PATCH linux-next v2] net: ath5k: replace ternary operator with min() Guo Zhengkui
2022-05-22 12:29 ` Kalle Valo
2022-05-17 2:41 ` [PATCH linux-next v2] net: ath9k: replace ternary operator with max() Guo Zhengkui
2022-05-17 10:24 ` Toke Høiland-Jørgensen
2022-05-22 12:31 ` Kalle Valo
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=874k1pxvca.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guozhengkui@vivo.com \
--cc=jirislaby@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mickflemm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toke@toke.dk \
--cc=zhengkui_guo@outlook.com \
/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).