netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Piotr Kwapulinski <piotr.kwapulinski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [PATCH iwl-next v10 5/7] ixgbe: Add ixgbe_x540 multiple header inclusion protection
Date: Thu, 24 Oct 2024 14:39:15 +0100	[thread overview]
Message-ID: <20241024133915.GP1202098@kernel.org> (raw)
In-Reply-To: <20241023124358.6967-6-piotr.kwapulinski@intel.com>

On Wed, Oct 23, 2024 at 02:43:56PM +0200, Piotr Kwapulinski wrote:
> Required to adopt x540 specific functions by E610 device.
> 
> Signed-off-by: Piotr Kwapulinski <piotr.kwapulinski@intel.com>

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


  reply	other threads:[~2024-10-24 13:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 12:43 [PATCH iwl-next v10 0/7] ixgbe: Add support for Intel(R) E610 device Piotr Kwapulinski
2024-10-23 12:43 ` [PATCH iwl-next v10 1/7] ixgbe: Add support for E610 FW Admin Command Interface Piotr Kwapulinski
2024-10-23 12:43 ` [PATCH iwl-next v10 2/7] ixgbe: Add support for E610 device capabilities detection Piotr Kwapulinski
2024-10-24 13:38   ` Simon Horman
2024-10-23 12:43 ` [PATCH iwl-next v10 3/7] ixgbe: Add link management support for E610 device Piotr Kwapulinski
2024-10-23 12:43 ` [PATCH iwl-next v10 4/7] ixgbe: Add support for NVM handling in " Piotr Kwapulinski
2024-10-23 12:43 ` [PATCH iwl-next v10 5/7] ixgbe: Add ixgbe_x540 multiple header inclusion protection Piotr Kwapulinski
2024-10-24 13:39   ` Simon Horman [this message]
2024-10-23 12:43 ` [PATCH iwl-next v10 6/7] ixgbe: Clean up the E610 link management related code Piotr Kwapulinski
2024-10-23 12:43 ` [PATCH iwl-next v10 7/7] ixgbe: Enable link management in E610 device Piotr Kwapulinski

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=20241024133915.GP1202098@kernel.org \
    --to=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=netdev@vger.kernel.org \
    --cc=piotr.kwapulinski@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;
as well as URLs for NNTP newsgroup(s).