From: Jakub Kicinski <kuba@kernel.org>
To: Qianfeng Rong <rongqianfeng@vivo.com>
Cc: "Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Potnuri Bharat Teja" <bharat@chelsio.com>,
"Veerasenareddy Burru" <vburru@marvell.com>,
"Sathesh Edara" <sedara@marvell.com>,
"Louis Peens" <louis.peens@corigine.com>,
"Shahed Shaikh" <shshaikh@marvell.com>,
"Manish Chopra" <manishc@marvell.com>,
GR-Linux-NIC-Dev@marvell.com (maintainer:QLOGIC QLCNIC (1/10)Gb
ETHERNET DRIVER), "Jiri Slaby" <jirislaby@kernel.org>,
"Nick Kossifidis" <mickflemm@gmail.com>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
"Arend van Spriel" <arend.vanspriel@broadcom.com>,
"Brian Norris" <briannorris@chromium.org>,
"Francesco Dolcini" <francesco@dolcini.it>,
"Ajay Singh" <ajay.kathat@microchip.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
"Ping-Ke Shih" <pkshih@realtek.com>,
"Kees Cook" <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Kory Maincent" <kory.maincent@bootlin.com>,
"Aleksander Jan Bajkowski" <olek2@wp.pl>,
"Lucas Sanchez Sagrado" <lucsansag@gmail.com>,
"Philipp Hahn" <phahn-oss@avm.de>,
"Eric Biggers" <ebiggers@google.com>,
"Hayes Wang" <hayeswang@realtek.com>,
"Wentao Liang" <vulab@iscas.ac.cn>,
"Johannes Berg" <johannes.berg@intel.com>,
"Sai Krishna" <saikrishnag@marvell.com>,
"Jacobe Zang" <jacobe.zang@wesion.com>,
"Dmitry Antipov" <dmantipov@yandex.ru>,
"Kalle Valo" <kvalo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"David Lin" <yu-hao.lin@nxp.com>,
"Aditya Kumar Singh" <quic_adisi@quicinc.com>,
"Roopni Devanathan" <quic_rdevanat@quicinc.com>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Marek Vasut" <marex@denx.de>,
"Alexis Lothoré" <alexis.lothore@bootlin.com>,
"Arnd Bergmann" <arnd@arndb.de>,
netdev@vger.kernel.org (open list:CAVIUM LIQUIDIO NETWORK DRIVER),
linux-kernel@vger.kernel.org (open list),
oss-drivers@corigine.com (open list:NETRONOME ETHERNET DRIVERS),
linux-usb@vger.kernel.org (open list:USB NETWORKING DRIVERS),
linux-wireless@vger.kernel.org (open list:ATHEROS ATH5K WIRELESS
DRIVER),
brcm80211@lists.linux.dev (open list:BROADCOM BRCM80211
IEEE802.11 WIRELESS DRIVERS),
brcm80211-dev-list.pdl@broadcom.com (open list:BROADCOM
BRCM80211 IEEE802.11 WIRELESS DRIVERS)
Subject: Re: [PATCH 00/12] net: Use min()/max() to improve code
Date: Thu, 10 Jul 2025 17:59:21 -0700 [thread overview]
Message-ID: <20250710175921.09212fab@kernel.org> (raw)
In-Reply-To: <20250709022210.304030-1-rongqianfeng@vivo.com>
On Wed, 9 Jul 2025 10:21:28 +0800 Qianfeng Rong wrote:
> Use min() to reduce the code and improve its readability.
>
> No functional changes.
For net/ethernet/ this is not worth the churn, sorry.
next prev parent reply other threads:[~2025-07-11 0:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 2:21 [PATCH 00/12] net: Use min()/max() to improve code Qianfeng Rong
2025-07-09 2:21 ` [PATCH 07/12] wifi: ath5k: Use max() " Qianfeng Rong
2025-07-09 4:55 ` Jiri Slaby
2025-07-09 2:21 ` [PATCH 08/12] wifi: ath9k: " Qianfeng Rong
2025-07-09 2:21 ` [PATCH 09/12] wifi: brcm80211: Use min() " Qianfeng Rong
2025-07-09 2:21 ` [PATCH 10/12] wifi: mwifiex: Use max() " Qianfeng Rong
2025-07-09 5:42 ` Jeff Chen
2025-07-09 6:42 ` Qianfeng Rong
2025-07-09 2:21 ` [PATCH 11/12] wifi: wilc1000: Use min() " Qianfeng Rong
2025-07-09 13:58 ` Alexis Lothoré
2025-07-09 2:21 ` [PATCH 12/12] wifi: rtlwifi: Use min()/max() " Qianfeng Rong
2025-07-09 6:57 ` Ping-Ke Shih
2025-07-11 0:59 ` Jakub Kicinski [this message]
2025-07-14 2:08 ` [PATCH 00/12] net: " Qianfeng Rong
-- strict thread matches above, loose matches on Subject: below --
2025-07-08 13:55 Qianfeng Rong
2025-07-08 14:12 ` Jakub Kicinski
2025-07-08 14:15 ` Qianfeng Rong
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=20250710175921.09212fab@kernel.org \
--to=kuba@kernel.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=ajay.kathat@microchip.com \
--cc=alexis.lothore@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=arend.vanspriel@broadcom.com \
--cc=arnd@arndb.de \
--cc=bharat@chelsio.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=briannorris@chromium.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=dmantipov@yandex.ru \
--cc=ebiggers@google.com \
--cc=edumazet@google.com \
--cc=francesco@dolcini.it \
--cc=gustavoars@kernel.org \
--cc=hayeswang@realtek.com \
--cc=jacobe.zang@wesion.com \
--cc=jirislaby@kernel.org \
--cc=johannes.berg@intel.com \
--cc=kees@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=louis.peens@corigine.com \
--cc=lucsansag@gmail.com \
--cc=manishc@marvell.com \
--cc=marex@denx.de \
--cc=mcgrof@kernel.org \
--cc=mickflemm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=phahn-oss@avm.de \
--cc=pkshih@realtek.com \
--cc=quic_adisi@quicinc.com \
--cc=quic_rdevanat@quicinc.com \
--cc=rongqianfeng@vivo.com \
--cc=s.hauer@pengutronix.de \
--cc=saikrishnag@marvell.com \
--cc=sedara@marvell.com \
--cc=shshaikh@marvell.com \
--cc=toke@toke.dk \
--cc=vburru@marvell.com \
--cc=vulab@iscas.ac.cn \
--cc=yu-hao.lin@nxp.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).