All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>, netdev@vger.kernel.org
Subject: [PATCH net-next 0/2][pull request] Intel Wired LAN Driver Updates 2022-08-18 (ixgbe)
Date: Thu, 18 Aug 2022 15:34:00 -0700	[thread overview]
Message-ID: <20220818223402.1294091-1-anthony.l.nguyen@intel.com> (raw)

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.

The following are changes since commit e34cfee65ec891a319ce79797dda18083af33a76:
  stmmac: intel: remove unused 'has_crossts' flag
and are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue 10GbE

Fabio M. De Francesco (1):
  ixgbe: Don't call kmap() on page allocated with GFP_ATOMIC

Jeff Daly (1):
  ixgbe: Manual AN-37 for troublesome link partners for X550 SFI

 .../net/ethernet/intel/ixgbe/ixgbe_ethtool.c  |  4 +-
 drivers/net/ethernet/intel/ixgbe/ixgbe_type.h |  3 +
 drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c | 56 ++++++++++++++++++-
 3 files changed, 57 insertions(+), 6 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-08-18 22:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 22:34 Tony Nguyen [this message]
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 ` [PATCH net-next 0/2][pull request] Intel Wired LAN Driver Updates 2022-08-18 (ixgbe) patchwork-bot+netdevbpf

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=20220818223402.1294091-1-anthony.l.nguyen@intel.com \
    --to=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.