From: Stephen Hemminger <stephen@networkplumber.org>
To: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
Cc: dev@dpdk.org, kishore.padmanabha@broadcom.com, stable@dpdk.org,
Keegan Freyhof <keegan.freyhof@broadcom.com>
Subject: Re: [PATCH 1/5] net/bnxt: fix NQ/CQ processing for interrupt handling
Date: Wed, 3 Jun 2026 14:43:41 -0700 [thread overview]
Message-ID: <20260603144341.23867ee2@phoenix.local> (raw)
In-Reply-To: <20260603211341.2112344-2-Mohammad-Shuab.Siddique@broadcom.com>
On Wed, 3 Jun 2026 15:13:37 -0600
Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com> wrote:
> +void bnxt_process_async_msg(struct bnxt *bp, struct tx_cmpl *cmpl)
> +{
> + uint16_t type = cmpl->flags_type & TX_CMPL_TYPE_MASK;
> +
> + switch (type) {
> + case HWRM_CMPL_TYPE_HWRM_DONE:
> + break;
> + case HWRM_ASYNC_EVENT_CMPL_TYPE_HWRM_ASYNC_EVENT:
> + bnxt_handle_async_event(bp, (struct cmpl_base *)cmpl);
> + break;
> + default:
> + printf("Port:%d Unhandled async message %x\n", bp->eth_dev->data->port_id, type);
> + break;
> + }
> +}
NAK
printf is not allowed in DPDK code, use proper logging
next prev parent reply other threads:[~2026-06-03 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 21:13 [PATCH 0/5] net/bnxt: interrupt handling, external mbuf and stability fixes Mohammad Shuab Siddique
2026-06-03 21:13 ` [PATCH 1/5] net/bnxt: fix NQ/CQ processing for interrupt handling Mohammad Shuab Siddique
2026-06-03 21:43 ` Stephen Hemminger [this message]
2026-06-03 21:13 ` [PATCH 2/5] net/bnxt: use buf address for external mbuf Mohammad Shuab Siddique
2026-06-03 21:43 ` Stephen Hemminger
2026-06-03 21:13 ` [PATCH 3/5] net/bnxt: fix IOVA range check for external mbuf head node Mohammad Shuab Siddique
2026-06-03 21:13 ` [PATCH 4/5] net/bnxt: prevent a potential segfault Mohammad Shuab Siddique
2026-06-03 21:13 ` [PATCH 5/5] net/bnxt: fix for segmentation fault that would occur on exit Mohammad Shuab Siddique
2026-06-05 0:50 ` [PATCH v2 0/5] net/bnxt: interrupt handling, external mbuf and stability fixes Mohammad Shuab Siddique
2026-06-05 0:50 ` [PATCH v2 1/5] net/bnxt: fix NQ/CQ processing for interrupt handling Mohammad Shuab Siddique
2026-06-05 0:50 ` [PATCH v2 2/5] net/bnxt: use buf address for external mbuf Mohammad Shuab Siddique
2026-06-05 0:50 ` [PATCH v2 3/5] net/bnxt: fix IOVA range check for external mbuf head node Mohammad Shuab Siddique
2026-06-05 0:50 ` [PATCH v2 4/5] net/bnxt: prevent a potential segfault Mohammad Shuab Siddique
2026-06-05 0:50 ` [PATCH v2 5/5] net/bnxt: fix for segmentation fault that would occur on exit Mohammad Shuab Siddique
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=20260603144341.23867ee2@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=keegan.freyhof@broadcom.com \
--cc=kishore.padmanabha@broadcom.com \
--cc=mohammad-shuab.siddique@broadcom.com \
--cc=stable@dpdk.org \
/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