Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932339AbdGSL3H (ORCPT ); Wed, 19 Jul 2017 07:29:07 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:37167 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754192AbdGSL3E (ORCPT ); Wed, 19 Jul 2017 07:29:04 -0400 Date: Wed, 19 Jul 2017 13:28:12 +0200 From: Daniel Kiper To: Greg Kroah-Hartman Cc: 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, Ingo Molnar Subject: Re: [PATCH 4.12 26/84] x86/xen/efi: Initialize only the EFI struct members used by Xen Message-ID: <20170719112812.GB4448@olila.local.net-space.pl> References: <20170719092322.362625377@linuxfoundation.org> <20170719092323.396710042@linuxfoundation.org> <20170719103747.GZ4448@olila.local.net-space.pl> <20170719111214.GA11941@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170719111214.GA11941@kroah.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: aserv0022.oracle.com [141.146.126.234] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 731 Lines: 21 On Wed, Jul 19, 2017 at 01:12:14PM +0200, Greg Kroah-Hartman wrote: > On Wed, Jul 19, 2017 at 12:37:47PM +0200, 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. > > Are you sure it actually applied? (hint, it did not...) > > If you want it in 4.11, or older kernels, please provide a working > backport. OK, if it did not apply then probably there were some changes in the code here and there. Though, IIRC, fix itself is perfectly valid for 4.11. So, I will post updated patch for it. Thanks, Daniel