public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel•org>
To: Kurt Kanzenbach <kurt@linutronix•de>
Cc: Jesse Brandeburg <jesse.brandeburg@intel•com>,
	Tony Nguyen <anthony.l.nguyen@intel•com>,
	Vinicius Costa Gomes <vinicius.gomes@intel•com>,
	"David S. Miller" <davem@davemloft•net>,
	Eric Dumazet <edumazet@google•com>,
	Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
	intel-wired-lan@lists•osuosl.org, netdev@vger•kernel.org,
	Sebastian Andrzej Siewior <bigeasy@linutronix•de>
Subject: Re: [PATCH v2 iwl-next 2/3] igc: Use netdev printing functions for flex filters
Date: Thu, 25 Jan 2024 11:59:09 +0000	[thread overview]
Message-ID: <20240125115909.GK217708@kernel.org> (raw)
In-Reply-To: <20240124085532.58841-3-kurt@linutronix.de>

On Wed, Jan 24, 2024 at 09:55:31AM +0100, Kurt Kanzenbach wrote:
> All igc filter implementations use netdev_*() printing functions except for
> the flex filters. Unify it.
> 
> Signed-off-by: Kurt Kanzenbach <kurt@linutronix•de>
> Acked-by: Vinicius Costa Gomes <vinicius.gomes@intel•com>

Reviewed-by: Simon Horman <horms@kernel•org>


  reply	other threads:[~2024-01-25 11:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24  8:55 [PATCH v2 iwl-next 0/3] igc: ethtool: Flex filter cleanup Kurt Kanzenbach
2024-01-24  8:55 ` [PATCH v2 iwl-next 1/3] igc: Use reverse xmas tree Kurt Kanzenbach
2024-01-25 11:58   ` Simon Horman
2024-02-04 10:40   ` [Intel-wired-lan] " naamax.meir
2024-01-24  8:55 ` [PATCH v2 iwl-next 2/3] igc: Use netdev printing functions for flex filters Kurt Kanzenbach
2024-01-25 11:59   ` Simon Horman [this message]
2024-02-04 15:05   ` [Intel-wired-lan] " naamax.meir
2024-01-24  8:55 ` [PATCH v2 iwl-next 3/3] igc: Unify filtering rule fields Kurt Kanzenbach
2024-01-25 11:59   ` Simon Horman
2024-02-04 20:08   ` [Intel-wired-lan] " naamax.meir

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=20240125115909.GK217708@kernel.org \
    --to=horms@kernel$(echo .)org \
    --cc=anthony.l.nguyen@intel$(echo .)com \
    --cc=bigeasy@linutronix$(echo .)de \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=intel-wired-lan@lists$(echo .)osuosl.org \
    --cc=jesse.brandeburg@intel$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=kurt@linutronix$(echo .)de \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=vinicius.gomes@intel$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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