From: Bruce Richardson <bruce.richardson@intel.com>
To: Arin Kharkar <arinkharkar@gmail.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] FIX: excessive logging in I40E driver
Date: Fri, 22 May 2026 15:49:10 +0100 [thread overview]
Message-ID: <ahBs5sVdRubjqpO5@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260512234227.218761-1-arinkharkar@gmail.com>
On Tue, May 12, 2026 at 04:42:27PM -0700, Arin Kharkar wrote:
> Resolved bug #1936 by changing the log level in i40e_set_tx_function from NOTICE to DEBUG
> ---
> drivers/net/intel/i40e/i40e_rxtx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/intel/i40e/i40e_rxtx.c b/drivers/net/intel/i40e/i40e_rxtx.c
> index c5ac75e0f0..bc48303a25 100644
> --- a/drivers/net/intel/i40e/i40e_rxtx.c
> +++ b/drivers/net/intel/i40e/i40e_rxtx.c
> @@ -3124,7 +3124,7 @@ i40e_set_tx_function(struct rte_eth_dev *dev)
> i40e_tx_path_infos[ad->tx_func_type].pkt_burst;
> dev->tx_pkt_prepare = i40e_tx_path_infos[ad->tx_func_type].pkt_prep;
>
> - PMD_DRV_LOG(NOTICE, "Using %s (port %d).",
> + PMD_DRV_LOG(DEBUG, "Using %s (port %d).",
> i40e_tx_path_infos[ad->tx_func_type].info, dev->data->port_id);
>
> if (ad->tx_func_type == I40E_TX_SCALAR_SIMPLE ||
Hi, thanks for the fix.
Unfortunately, with the recent changes in the drivers to use a different
path selection mechanism, this patch is no longer relevant, I believe. The
log messages for path selection in the driver on "next-net-intel" tree are
now all at DEBUG level.
Marking as not-applicable in patchwork.
Thanks,
/Bruce
prev parent reply other threads:[~2026-05-22 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 23:42 [PATCH] FIX: excessive logging in I40E driver Arin Kharkar
2026-05-22 14:49 ` Bruce Richardson [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=ahBs5sVdRubjqpO5@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=arinkharkar@gmail.com \
--cc=dev@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