From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [net-next 0/4][pull request] 1GbE Intel Wired LAN Driver Updates 2017-04-30
Date: Sun, 30 Apr 2017 11:35:52 -0400 (EDT) [thread overview]
Message-ID: <20170430.113552.1370074918240589323.davem@davemloft.net> (raw)
In-Reply-To: <20170430123614.67897-1-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Sun, 30 Apr 2017 05:36:10 -0700
> This series contains updates to e1000e only.
>
> Jarod Wilson fixes an issue where the workaround for 82574 & 82583
> is needed for i218 as well, so set the appropriate flags.
>
> Sasha adds support for the upcoming new i219 devices for the client
> platform (CannonLake), which includes the support for 38.4MHz frequency
> to support PTP on CannonLake.
>
> The following are changes since commit c08bac03d2894113bdb114e66e6ada009defb120:
> Merge branch '10GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 1GbE
Pulled.
prev parent reply other threads:[~2017-04-30 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 12:36 [net-next 0/4][pull request] 1GbE Intel Wired LAN Driver Updates 2017-04-30 Jeff Kirsher
2017-04-30 12:36 ` [net-next 1/4] e1000e: fix PTP on e1000_pch_lpt variants Jeff Kirsher
2017-04-30 12:36 ` [net-next 2/4] e1000e: Initial Support for CannonLake Jeff Kirsher
2017-04-30 12:36 ` [net-next 3/4] e1000e: Add " Jeff Kirsher
2017-04-30 12:36 ` [net-next 4/4] e1000e: Add Support for 38.4MHZ frequency Jeff Kirsher
2017-04-30 15:35 ` David Miller [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=20170430.113552.1370074918240589323.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--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).