From: Greg KH <greg@kroah.com>
To: Pat Riehecky <riehecky@fnal.gov>
Cc: stable@vger.kernel.org, Raanan Avargil <raanan.avargil@intel.com>,
Aaron Brown <aaron.f.brown@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: f3ed935de e1000e: Initial support for KabeLake
Date: Thu, 14 Mar 2019 13:08:29 -0700 [thread overview]
Message-ID: <20190314200829.GB16125@kroah.com> (raw)
In-Reply-To: <16ecaae0-5552-2c86-1a3a-7012266984a7@fnal.gov>
On Thu, Mar 14, 2019 at 02:34:17PM -0500, Pat Riehecky wrote:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9cd34b3a1
>
> The additional hardware support would be helpful in the 4.4 long term tree.
>
> e1000e: Initial support for KabeLake
> i219 (4) and i219 (5) are the next LOM generations that will be
> available on the next Intel platform (KabeLake).
> This patch provides the initial support for the devices.
>
> Signed-off-by: Raanan Avargil <raanan.avargil@intel.com>
> Tested-by: Aaron Brown <aaron.f.brown@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Does this patch work properly on 4.4.y for this hardware with just this
patch?
Also, always cc: the authors of the patch when asking for them to be
added to stable, to get their opinion/objection if needed.
thanks,
greg k-h
next prev parent reply other threads:[~2019-03-14 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 19:34 f3ed935de e1000e: Initial support for KabeLake Pat Riehecky
2019-03-14 20:08 ` Greg KH [this message]
2019-03-14 21:17 ` Jeff Kirsher
2019-03-14 21:54 ` Greg KH
2019-03-14 22:53 ` Jeff Kirsher
2019-03-14 23:25 ` Greg KH
2019-03-15 1:36 ` Jeff Kirsher
2019-03-15 13:13 ` Pat Riehecky
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=20190314200829.GB16125@kroah.com \
--to=greg@kroah.com \
--cc=aaron.f.brown@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=raanan.avargil@intel.com \
--cc=riehecky@fnal.gov \
--cc=stable@vger.kernel.org \
/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