Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935837AbdGTJlR (ORCPT ); Thu, 20 Jul 2017 05:41:17 -0400 Received: from mail-wr0-f194.google.com ([209.85.128.194]:33504 "EHLO mail-wr0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934105AbdGTJlO (ORCPT ); Thu, 20 Jul 2017 05:41:14 -0400 Date: Thu, 20 Jul 2017 11:41:10 +0200 From: Ingo Molnar To: Greg Kroah-Hartman Cc: Daniel Kiper , linux-kernel@vger.kernel.org, stable@vger.kernel.org, Boris Ostrovsky , Ard Biesheuvel , Linus Torvalds , Peter Zijlstra , Thomas Gleixner , andrew.cooper3@citrix.com, jgross@suse.com, linux-efi@vger.kernel.org, matt@codeblueprint.co.uk, xen-devel@lists.xenproject.org Subject: Re: [PATCH 4.12 26/84] x86/xen/efi: Initialize only the EFI struct members used by Xen Message-ID: <20170720094110.sy552pxras33wig5@gmail.com> References: <20170719092322.362625377@linuxfoundation.org> <20170719092323.396710042@linuxfoundation.org> <20170719103747.GZ4448@olila.local.net-space.pl> <20170720083910.aygobq7t7g7laszt@gmail.com> <20170720091639.GA1071@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170720091639.GA1071@kroah.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 986 Lines: 30 * Greg Kroah-Hartman wrote: > On Thu, Jul 20, 2017 at 10:39:10AM +0200, Ingo Molnar wrote: > > > > * Daniel Kiper wrote: > > > > > Hey Greg, > > > > > > On Wed, Jul 19, 2017 at 11:43:32AM +0200, Greg Kroah-Hartman wrote: > > > > 4.12-stable review patch. If anyone has any objections, please let me know. > > > > > > Why did you skip this patch for 4.11? IMO it should be applied there too. > > > > The thing is, this patch should probaly not even be in v4.12, as it should only > > make any difference if there's a separate _bug_ in the kernel. > > > > This patch makes things more robust going forward, but I question that it needs to > > be in -stable. > > Yeah, good point, I'm going to go drop it entirely from the 4.12-stable > tree as it obviously isn't stable material, sorry for not catching that > before. I should have caught the tag as well when applying the upstream patch to begin with. Thanks! Ingo