From: Greg KH <gregkh@linuxfoundation.org>
To: Ajay Kaher <akaher@vmware.com>
Cc: "kys@microsoft.com" <kys@microsoft.com>,
"haiyangz@microsoft.com" <haiyangz@microsoft.com>,
"jloeser@microsoft.com" <jloeser@microsoft.com>,
"sthemmin@microsoft.com" <sthemmin@microsoft.com>,
"sashal@kernel.org" <sashal@kernel.org>,
"mikelley@microsoft.com" <mikelley@microsoft.com>,
"decui@microsoft.com" <decui@microsoft.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Srivatsa Bhat <srivatsab@vmware.com>,
Alexey Makhalov <amakhalov@vmware.com>
Subject: Re: [PATCH 0/3] PCI: hv: Use vPCI protocol version 1.2 for v4.9
Date: Wed, 23 Jan 2019 13:08:52 +0100 [thread overview]
Message-ID: <20190123120852.GA19317@kroah.com> (raw)
In-Reply-To: <3CDA15D0-3D01-42FA-84D6-83A3FB6E7A16@vmware.com>
On Wed, Jan 23, 2019 at 12:02:27PM +0000, Ajay Kaher wrote:
>
>
> On 23/01/19, 1:33 PM, "Greg KH" <gregkh@linuxfoundation.org> wrote:
>
> On Wed, Jan 23, 2019 at 09:08:29PM +0530, Ajay Kaher wrote:
> > For now, please consider these patches for review and
> > suggest if these can be merged to mainline kernel v4.9.
>
> Why do you care about 4.9.y? Shouldn't all of your systems be moved on
> to 4.14.y or better yet, 4.19.y, at this point in time? 4.9.y is
> _really_ old and obsolete and on the very cusp of "never run as a
> general-purpose system" functionality, if it's not already there.
>
> What is preventing you from upgrading the kernel on your systems to
> something more modern and secure?
>
> Yes Greg, we are working to move to latest Linux Kernel versions.
> But on other side, because of demands from our consumers we also need to support v4.9.
Why would a customer "demand" that 4.9 still be used? What is keeping
them from just moving to a newer kernel today? What is missing in 4.14
or 4.19 that only 4.9 has?
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-23 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 15:38 [PATCH 0/3] PCI: hv: Use vPCI protocol version 1.2 for v4.9 Ajay Kaher
2019-01-23 8:00 ` Greg KH
2019-01-23 8:02 ` Greg KH
2019-01-23 12:02 ` Ajay Kaher
2019-01-23 12:08 ` Greg KH [this message]
2019-01-23 15:38 ` [PATCH 1/3] PCI: hv: Allocate physically contiguous hypercall params buffer Ajay Kaher
2019-01-23 8:01 ` Greg KH
2019-01-23 15:38 ` [PATCH 2/3] PCI: hv: Add vPCI version protocol negotiation Ajay Kaher
2019-01-23 15:38 ` [PATCH 3/3] PCI: hv: Use vPCI protocol version 1.2 for v4.9 Ajay Kaher
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=20190123120852.GA19317@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akaher@vmware.com \
--cc=amakhalov@vmware.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jloeser@microsoft.com \
--cc=kys@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=sashal@kernel.org \
--cc=srivatsab@vmware.com \
--cc=stable@vger.kernel.org \
--cc=sthemmin@microsoft.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).