From: Somnath Kotur <somnath.kotur@broadcom.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: Alok Tiwari <alok.a.tiwari@oracle.com>,
pavan.chebbi@broadcom.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] bnxt_en: fix incorrect page count in RX aggr ring log
Date: Fri, 29 Aug 2025 08:24:55 +0530 [thread overview]
Message-ID: <CAOBf=mt4NovRDJHbU_e7XQvvYvDtvLdJmkLDsWhQCKrQ1=jZ-w@mail.gmail.com> (raw)
In-Reply-To: <CACKFLimOb++PxzBSZcLHP1GQP0wk+hK0XAoXti7DMLtRw4JQAw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
On Fri, Aug 29, 2025 at 6:01 AM Michael Chan <michael.chan@broadcom.com> wrote:
>
> On Thu, Aug 28, 2025 at 12:49 PM Alok Tiwari <alok.a.tiwari@oracle.com> wrote:
> >
> > The warning in bnxt_alloc_one_rx_ring_netmem() reports the number
> > of pages allocated for the RX aggregation ring. However, it
> > mistakenly used bp->rx_ring_size instead of bp->rx_agg_ring_size,
> > leading to confusing or misleading log output.
> >
> > Use the correct bp->rx_agg_ring_size value to fix this.
> >
> > Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
>
> Reviewed-by: Michael Chan <michael.chan@broadcom.com>
Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
>
> Please add the Fixes tag since this is a bug fix. Thanks.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4199 bytes --]
prev parent reply other threads:[~2025-08-29 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 19:48 [PATCH net-next] bnxt_en: fix incorrect page count in RX aggr ring log Alok Tiwari
2025-08-28 21:38 ` Jacob Keller
2025-08-29 0:30 ` Michael Chan
2025-08-29 2:54 ` Somnath Kotur [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='CAOBf=mt4NovRDJHbU_e7XQvvYvDtvLdJmkLDsWhQCKrQ1=jZ-w@mail.gmail.com' \
--to=somnath.kotur@broadcom.com \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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).