DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Shaiq Wani <shaiq.wani@intel.com>
Cc: <dev@dpdk.org>, <aman.deep.singh@intel.com>
Subject: Re: [PATCH 0/4] net/intel: demote path selection logs from NOTICE to DEBUG
Date: Mon, 20 Apr 2026 17:54:11 +0100	[thread overview]
Message-ID: <aeZaM3DNu8GP0H58@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260420062746.178145-1-shaiq.wani@intel.com>

On Mon, Apr 20, 2026 at 11:57:42AM +0530, Shaiq Wani wrote:
> Demote Rx/Tx path selection messages from NOTICE to DEBUG level
> to reduce noise across ice, iavf, idpf and cpfl drivers.
> 
> Shaiq Wani (4):
>   net/ice: demote path selection logs from NOTICE to DEBUG
>   net/iavf: demote path selection logs from NOTICE to DEBUG
>   net/idpf: demote path selection logs from NOTICE to DEBUG
>   net/cpfl: demote path selection logs from NOTICE to DEBUG
> 
>  drivers/net/intel/cpfl/cpfl_rxtx.c | 4 ++--
>  drivers/net/intel/iavf/iavf_rxtx.c | 4 ++--
>  drivers/net/intel/ice/ice_rxtx.c   | 4 ++--
>  drivers/net/intel/idpf/idpf_rxtx.c | 4 ++--
>  4 files changed, 8 insertions(+), 8 deletions(-)
> 
Reasonable change, to match those proposed by Stephen for i40e.
However, I don't view these as bugfixes and don't believe they should be
backported, so dropping the fixes lines and Cc of stable in each patch.

Series-Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Applied to dpdk-next-net-intel.
Thanks,
/Bruce

      parent reply	other threads:[~2026-04-20 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20  6:27 [PATCH 0/4] net/intel: demote path selection logs from NOTICE to DEBUG Shaiq Wani
2026-04-20  6:27 ` [PATCH 1/4] net/ice: " Shaiq Wani
2026-04-20  6:27 ` [PATCH 2/4] net/iavf: " Shaiq Wani
2026-04-20  6:27 ` [PATCH 3/4] net/idpf: " Shaiq Wani
2026-04-20  6:27 ` [PATCH 4/4] net/cpfl: " Shaiq Wani
2026-04-20 16:54 ` 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=aeZaM3DNu8GP0H58@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=shaiq.wani@intel.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