From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
netdev@vger.kernel.org, sassmann@redhat.com
Subject: [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2021-03-19
Date: Fri, 19 Mar 2021 09:19:54 -0700 [thread overview]
Message-ID: <20210319161957.784610-1-anthony.l.nguyen@intel.com> (raw)
This series contains updates to e1000e and igb drivers.
Tom Seewald fixes duplicate guard issues by including the driver name in
the guard for e1000e and igb.
Jesse adds checks that timestamping is on and valid to avoid possible
issues with a misinterpreted time stamp for igb.
The following are changes since commit c79a707072fe3fea0e3c92edee6ca85c1e53c29f:
net: cdc-phonet: fix data-interface release on probe failure
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue 1GbE
Jesse Brandeburg (1):
igb: check timestamp validity
Tom Seewald (2):
e1000e: Fix duplicate include guard
igb: Fix duplicate include guard
drivers/net/ethernet/intel/e1000e/hw.h | 6 ++---
drivers/net/ethernet/intel/igb/e1000_hw.h | 6 ++---
drivers/net/ethernet/intel/igb/igb.h | 4 +--
drivers/net/ethernet/intel/igb/igb_main.c | 11 ++++----
drivers/net/ethernet/intel/igb/igb_ptp.c | 31 ++++++++++++++++++-----
5 files changed, 38 insertions(+), 20 deletions(-)
--
2.26.2
next reply other threads:[~2021-03-19 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 16:19 Tony Nguyen [this message]
2021-03-19 16:19 ` [PATCH net 1/3] e1000e: Fix duplicate include guard Tony Nguyen
2021-03-19 16:19 ` [PATCH net 2/3] igb: " Tony Nguyen
2021-03-19 16:19 ` [PATCH net 3/3] igb: check timestamp validity Tony Nguyen
2021-03-19 21:00 ` [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2021-03-19 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=20210319161957.784610-1-anthony.l.nguyen@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sassmann@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 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).