From: Greg KH <gregkh@linuxfoundation.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: stable@vger.kernel.org
Subject: Re: [stable 4.19 0/4] Intel Wired Ethernet Fixes for 4.19.y
Date: Sat, 2 Feb 2019 10:00:57 +0100 [thread overview]
Message-ID: <20190202090057.GA32163@kroah.com> (raw)
In-Reply-To: <20190201205029.11855-1-jeffrey.t.kirsher@intel.com>
On Fri, Feb 01, 2019 at 12:50:25PM -0800, Jeff Kirsher wrote:
> This series contains backports and partial backports for the Intel ice
> driver.
>
> These backports are required to get the ice driver to load on the
> current hardware. This is due to mismatches between the driver code and
> the firmware running on the devices. At the time of release of 4.19,
> hardware was not available for verification. Since the 4.19.y kernel is
> a LTS kernel, we want to ensure that users with our E800 devices will be
> able to have the in-kernel driver load and pass traffic, if running a
> 4.19 or later kernel.
>
> Anirudh Venkataramanan (4):
> ice: Update expected FW version
> ice: Updates to Tx scheduler code
> ice: Introduce ice_dev_onetime_setup
> ice: Set timeout when disabling queues
Can you respin these with the git commit ids of the upstream patches in
them so that we can properly include that in the patches?
thanks,
greg k-h
prev parent reply other threads:[~2019-02-02 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 20:50 [stable 4.19 0/4] Intel Wired Ethernet Fixes for 4.19.y Jeff Kirsher
2019-02-01 20:50 ` [stable 4.19 1/4] ice: Update expected FW version Jeff Kirsher
2019-02-02 9:02 ` Greg KH
2019-02-01 20:50 ` [stable 4.19 2/4] ice: Updates to Tx scheduler code Jeff Kirsher
2019-02-02 11:28 ` Greg KH
2019-02-08 23:46 ` Jeff Kirsher
2019-02-18 12:25 ` Greg KH
2019-02-19 15:57 ` Jeff Kirsher
2019-02-01 20:50 ` [stable 4.19 3/4] ice: Introduce ice_dev_onetime_setup Jeff Kirsher
2019-02-01 20:50 ` [stable 4.19 4/4] ice: Set timeout when disabling queues Jeff Kirsher
2019-02-02 9:00 ` Greg KH [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=20190202090057.GA32163@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jeffrey.t.kirsher@intel.com \
--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 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.