All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2][pull request] Intel Wired LAN Driver Updates 2022-08-18 (ixgbe)
Date: Tue, 23 Aug 2022 03:30:16 +0000	[thread overview]
Message-ID: <166122541651.23241.4907877931835123588.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220818223402.1294091-1-anthony.l.nguyen@intel.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:

On Thu, 18 Aug 2022 15:34:00 -0700 you wrote:
> This series contains updates to ixgbe driver only.
> 
> Fabio M. De Francesco replaces kmap() call to page_address() for
> rx_buffer->page().
> 
> Jeff Daly adds a manual AN-37 restart to help resolve issues with some link
> partners.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] ixgbe: Don't call kmap() on page allocated with GFP_ATOMIC
    https://git.kernel.org/netdev/net-next/c/03f51719df03
  - [net-next,2/2] ixgbe: Manual AN-37 for troublesome link partners for X550 SFI
    https://git.kernel.org/netdev/net-next/c/565736048bd5

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



      parent reply	other threads:[~2022-08-23  3:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 22:34 [PATCH net-next 0/2][pull request] Intel Wired LAN Driver Updates 2022-08-18 (ixgbe) Tony Nguyen
2022-08-18 22:34 ` [PATCH net-next 1/2] ixgbe: Don't call kmap() on page allocated with GFP_ATOMIC Tony Nguyen
2022-08-18 22:34 ` [PATCH net-next 2/2] ixgbe: Manual AN-37 for troublesome link partners for X550 SFI Tony Nguyen
2022-08-23  3:30 ` patchwork-bot+netdevbpf [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=166122541651.23241.4907877931835123588.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.