mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: przemyslaw.kitszel@intel.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, emil.s.tantilov@intel.com,
	aleksander.lobakin@intel.com, willemb@google.com,
	sridhar.samudrala@intel.com, phani.r.burra@intel.com,
	piotr.kwapulinski@intel.com, horms@kernel.org,
	radoslawx.tyl@intel.com, jedrzej.jagielski@intel.com,
	konstantin.ilichev@intel.com, milena.olech@intel.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	aleksandr.loktionov@intel.com, Samuel.salin@intel.com,
	stable@vger.kernel.org, rafal.romanowski@intel.com,
	den@valinux.co.jp, sx.rinitha@intel.com, pmenzel@molgen.mpg.de
Subject: Re: [PATCH net v3 0/6] Intel Wired LAN Driver Updates 2025-10-01 (idpf, ixgbe, ixgbevf)
Date: Tue, 14 Oct 2025 01:10:35 +0000	[thread overview]
Message-ID: <176040423576.3390136.9978557000620458920.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251009-jk-iwl-net-2025-10-01-v3-0-ef32a425b92a@intel.com>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 09 Oct 2025 17:03:45 -0700 you wrote:
> For idpf:
> Milena fixes a memory leak in the idpf reset logic when the driver resets
> with an outstanding Tx timestamp.
> 
> For ixgbe and ixgbevf:
> Jedrzej fixes an issue with reporting link speed on E610 VFs.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/6] idpf: cleanup remaining SKBs in PTP flows
    https://git.kernel.org/netdev/net/c/a3f8c0a27312
  - [net,v3,2/6] ixgbevf: fix getting link speed data for E610 devices
    (no matching commit)
  - [net,v3,3/6] ixgbe: handle IXGBE_VF_GET_PF_LINK_STATE mailbox operation
    https://git.kernel.org/netdev/net/c/f7f97cbc03a4
  - [net,v3,4/6] ixgbevf: fix mailbox API compatibility by negotiating supported features
    https://git.kernel.org/netdev/net/c/a7075f501bd3
  - [net,v3,5/6] ixgbe: handle IXGBE_VF_FEATURES_NEGOTIATE mbox cmd
    https://git.kernel.org/netdev/net/c/823be089f9c8
  - [net,v3,6/6] ixgbe: fix too early devlink_free() in ixgbe_remove()
    https://git.kernel.org/netdev/net/c/5feef67b646d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-10-14  1:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10  0:03 Jacob Keller
2025-10-10  0:03 ` [PATCH net v3 1/6] idpf: cleanup remaining SKBs in PTP flows Jacob Keller
2025-10-10  0:03 ` [PATCH net v3 2/6] ixgbevf: fix getting link speed data for E610 devices Jacob Keller
2025-10-10  0:03 ` [PATCH net v3 3/6] ixgbe: handle IXGBE_VF_GET_PF_LINK_STATE mailbox operation Jacob Keller
2025-10-10  0:03 ` [PATCH net v3 4/6] ixgbevf: fix mailbox API compatibility by negotiating supported features Jacob Keller
2025-10-10  0:03 ` [PATCH net v3 5/6] ixgbe: handle IXGBE_VF_FEATURES_NEGOTIATE mbox cmd Jacob Keller
2025-10-10  0:03 ` [PATCH net v3 6/6] ixgbe: fix too early devlink_free() in ixgbe_remove() Jacob Keller
2025-10-14  1:10 ` patchwork-bot+netdevbpf [this message]
2025-10-14 23:20   ` [PATCH net v3 0/6] Intel Wired LAN Driver Updates 2025-10-01 (idpf, ixgbe, ixgbevf) Jacob Keller

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=176040423576.3390136.9978557000620458920.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Samuel.salin@intel.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=aleksandr.loktionov@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=den@valinux.co.jp \
    --cc=edumazet@google.com \
    --cc=emil.s.tantilov@intel.com \
    --cc=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jedrzej.jagielski@intel.com \
    --cc=konstantin.ilichev@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=milena.olech@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=phani.r.burra@intel.com \
    --cc=piotr.kwapulinski@intel.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=radoslawx.tyl@intel.com \
    --cc=rafal.romanowski@intel.com \
    --cc=sridhar.samudrala@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=sx.rinitha@intel.com \
    --cc=willemb@google.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

Powered by JetHome