From: Thomas Monjalon <thomas@monjalon.net>
To: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>,
Kishore Padmanabha <kishore.padmanabha@broadcom.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] net/bnxt: fix l2_db_multi_page_size_kb position in func_qcfg output
Date: Wed, 25 Mar 2026 15:17:36 +0100 [thread overview]
Message-ID: <4156142.taCxCBeP46@thomas> (raw)
In-Reply-To: <CA+BST0kjGN1rez_OWsrYdRHs0q=QiTv=s4iT7Xfq8Ag46PMDjw@mail.gmail.com>
24/03/2026 22:02, Kishore Padmanabha:
> On Tue, Mar 24, 2026 at 4:46 PM Mohammad Shuab Siddique <
> mohammad-shuab.siddique@broadcom.com> wrote:
>
> > From: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
> >
> > The field was placed at incorrect offset in hwrm_func_qcfg_output causing
> > legacy_l2_db_size_kb to read svif_info instead, producing a doorbell offset
> > exceeding BAR2 and resulting in SIGSEGV on BCM57608.
> >
> > Move l2_db_multi_page_size_kb after mirror_vnic_id to match firmware
> > response layout.
> >
> > Fixes: 04102f2ffc8c ("net/bnxt: update HWRM API to version 1.10.1.6")
looks not related
> > Fixes: 7a1f9c782b50 ("net/bnxt: add multi-doorbell support")
> >
> > Cc: stable@dpdk.org
not needed as it is only fixing a recent commit
> >
> > Signed-off-by: Mohammad Shuab Siddique <
> > mohammad-shuab.siddique@broadcom.com>
> >
> Acked-by: Kishore Padmanabha <kishore.padmanabha@broadcom.com>
Bugzilla ID: 1909
Reported-by: Oleksandr Nahnybida <oleksandrn@interfacemasters.com>
Applied, thanks.
prev parent reply other threads:[~2026-03-25 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 20:48 [PATCH] net/bnxt: fix l2_db_multi_page_size_kb position in func_qcfg output Mohammad Shuab Siddique
2026-03-24 21:02 ` Kishore Padmanabha
2026-03-25 14:17 ` Thomas Monjalon [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=4156142.taCxCBeP46@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=kishore.padmanabha@broadcom.com \
--cc=mohammad-shuab.siddique@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