From: Simon Horman <horms@kernel.org>
To: Yang Ruibin <11162571@vivo.com>
Cc: Chris Snook <chris.snook@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
opensource.kernel@vivo.com
Subject: Re: [PATCH v1] drivers:atlx:Use max macro
Date: Thu, 22 Aug 2024 13:53:55 +0100 [thread overview]
Message-ID: <20240822125355.GP2164@kernel.org> (raw)
In-Reply-To: <3f994754-2005-420d-9be4-33d7288bc811@vivo.com>
On Thu, Aug 22, 2024 at 05:40:28PM +0800, Yang Ruibin wrote:
> Sorry, please ignore this patch.
> Because the corresponding header file is not included, there may be
> compilation errors.
Hi Yang Ruibin,
Thanks for your patch.
Some feedback from a process point of view, for future reference.
1. Please do not top-post in emails to Kernel mailing lists.
2. As a Networking patch, that is not a bug fix, it should
be explicitly targeted at net-next.
Subject: [PATCH net-next] ...
3. Looking at git history, it looks like 'net: atheros: ' would be an
appropriate prefix for this patch.
Subject: [PATCH net-next] net: atheros: ...
Please consider reading
https://docs.kernel.org/process/maintainer-netdev.html
And please, if you do post a new version, allow 24h to pass since the you
posted this version (as described in the link above).
>
> 在 2024/8/22 15:50, Yang Ruibin 写道:
> > Instead of using the max() implementation of
> > the ternary operator, use real macros.
> >
> > Signed-off-by: Yang Ruibin <11162571@vivo.com>
> > ---
> > drivers/net/ethernet/atheros/atlx/atl2.c | 5 +----
> > 1 file changed, 1 insertion(+), 4 deletions(-)
> >
> > diff --git a/drivers/net/ethernet/atheros/atlx/atl2.c b/drivers/net/ethernet/atheros/atlx/atl2.c
> > index fa9a4919f..3ff669e72 100644
> > --- a/drivers/net/ethernet/atheros/atlx/atl2.c
> > +++ b/drivers/net/ethernet/atheros/atlx/atl2.c
> > @@ -2971,10 +2971,7 @@ static void atl2_check_options(struct atl2_adapter *adapter)
> > #endif
> > /* init RXD Flow control value */
> > adapter->hw.fc_rxd_hi = (adapter->rxd_ring_size / 8) * 7;
> > - adapter->hw.fc_rxd_lo = (ATL2_MIN_RXD_COUNT / 8) >
> > - (adapter->rxd_ring_size / 12) ? (ATL2_MIN_RXD_COUNT / 8) :
> > - (adapter->rxd_ring_size / 12);
> > -
> > + adapter->hw.fc_rxd_lo = max(ATL2_MIN_RXD_COUNT / 8, adapter->rxd_ring_size / 12);
Networking code still prefers lines to be 80 colimns wide or less.
In this case, I would suggest:
adapter->hw.fc_rxd_lo = max(ATL2_MIN_RXD_COUNT / 8,
adapter->rxd_ring_size / 12);
> > /* Interrupt Moderate Timer */
> > opt.type = range_option;
> > opt.name = "Interrupt Moderate Timer";
>
prev parent reply other threads:[~2024-08-22 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 7:50 [PATCH v1] drivers:atlx:Use max macro Yang Ruibin
2024-08-22 9:40 ` Yang Ruibin
2024-08-22 12:53 ` Simon Horman [this message]
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=20240822125355.GP2164@kernel.org \
--to=horms@kernel.org \
--cc=11162571@vivo.com \
--cc=chris.snook@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=pabeni@redhat.com \
--cc=sfr@canb.auug.org.au \
/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).