From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 14 Feb 2019 13:51:22 -0000 Received: from mail.kernel.org ([198.145.29.99]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1guHQ8-0007cZ-RY for speck@linutronix.de; Thu, 14 Feb 2019 14:51:21 +0100 Date: Thu, 14 Feb 2019 14:51:12 +0100 From: Greg KH Subject: [MODERATED] Re: [PATCH v5 00/27] MDSv5 19 Message-ID: <20190214135112.GA27902@kroah.com> References: <20190213223332.GL4516@lindsey> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Thu, Feb 14, 2019 at 02:09:41PM +0100, speck for Jiri Kosina wrote: > On Wed, 13 Feb 2019, speck for Tyler Hicks wrote: > > > Andi, I know you've been busy with the PERF changes but I'm curious if > > you plan to split up this series, as requested by Thomas? Intel is > > starting to ask software vendors when they might have beta builds of the > > mitigations available and my answer is going to depend on whether or not > > this split is going to be available soon. > > "Me too" from SUSE. > > We're being pushed by Intel to do testing and validating of ports to our > kernel branches, but we don't want to invest backporting effort into a > patchset that is not final. I'm telling people that keep asking me about "backports to the stable versions" that they should not do anything until we have a solid upstream-mergable version first. This pressure from Intel has got to stop, it's wasting people's time. greg k-h