From: Greg KH <gregkh@linuxfoundation.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: stable@vger.kernel.org,
Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>,
Tony Brelinski <tonyx.brelinski@intel.com>
Subject: Re: [stable 4.19 2/4] ice: Updates to Tx scheduler code
Date: Mon, 18 Feb 2019 13:25:05 +0100 [thread overview]
Message-ID: <20190218122505.GD30260@kroah.com> (raw)
In-Reply-To: <fe53b30f53eb301457a265197dfe08dbd1d307b1.camel@intel.com>
On Fri, Feb 08, 2019 at 03:46:26PM -0800, Jeff Kirsher wrote:
> On Sat, 2019-02-02 at 12:28 +0100, Greg KH wrote:
> > On Fri, Feb 01, 2019 at 12:50:27PM -0800, Jeff Kirsher wrote:
> > > From: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
> > >
> > > This is a backport of the mainline commit b36c598c999c ("ice:
> > > Updates to Tx scheduler code"). This change is required for the
> > > driver to work with the latest firmware. Without this patch,
> > > the driver fails probe.
> >
> > Note, this is a big change. You can't have these systems just run
> > the
> > old firmware? The fact that you require a kernel change for newer
> > firmware, isn't the best, you don't provide backwards compatibility
> > somehow?
> >
> > I'm all for adding new device ids and the like to stable kernels, but
> > to
> > backport new functionality just to get newer hardware to work on
> > older
> > kernels, is not the goal of the LTS kernel trees. Why can't you just
> > have users use 4.20 or newer? There shouldn't be anything keeping
> > them
> > from doing that and just updating to the latest stable release every
> > 4
> > months or so, right?
>
> Sorry Greg, I am not ignoring you. I have been trying to get more
> information and reasoning from others within Intel which needed this
> support within the 4.19 kernel. I am hoping I will have a response for
> you by Monday.
It's been more than one "Monday" now, so I'm dropping this series from
my patch queue.
thanks,
greg k-h
next prev parent reply other threads:[~2019-02-18 12:25 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 [this message]
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 ` [stable 4.19 0/4] Intel Wired Ethernet Fixes for 4.19.y Greg KH
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=20190218122505.GD30260@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anirudh.venkataramanan@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=stable@vger.kernel.org \
--cc=tonyx.brelinski@intel.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).