From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751581AbcCLGGA (ORCPT ); Sat, 12 Mar 2016 01:06:00 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:44691 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750712AbcCLGFw (ORCPT ); Sat, 12 Mar 2016 01:05:52 -0500 Date: Fri, 11 Mar 2016 22:05:49 -0800 From: Greg Kroah-Hartman To: Ard Biesheuvel Cc: "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , Will Deacon Subject: Re: [PATCH 4.4 34/74] arm64: vmemmap: use virtual projection of linear region Message-ID: <20160312060549.GA21794@kroah.com> References: <20160308000315.294406921@linuxfoundation.org> <20160308000316.386547682@linuxfoundation.org> <20160308134401.GA25309@kroah.com> <20160312055040.GB20808@kroah.com> <3BE88637-7CEF-4445-9CF0-5FCCB97507BE@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BE88637-7CEF-4445-9CF0-5FCCB97507BE@linaro.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 12, 2016 at 01:55:44PM +0800, Ard Biesheuvel wrote: > > > > On 12 mrt. 2016, at 13:50, Greg Kroah-Hartman wrote: > > > >> On Sat, Mar 12, 2016 at 08:51:26AM +0700, Ard Biesheuvel wrote: > >>> On 8 March 2016 at 20:45, Ard Biesheuvel wrote: > >>>> On 8 March 2016 at 20:44, Greg Kroah-Hartman wrote: > >>>>> On Tue, Mar 08, 2016 at 05:40:14PM +0700, Ard Biesheuvel wrote: > >>>>>> On 8 March 2016 at 07:02, Greg Kroah-Hartman wrote: > >>>>>> 4.4-stable review patch. If anyone has any objections, please let me know. > >>>>> > >>>>> Please hold off on this one. We are seeing some breakage on 64k pages systems > >>>> > >>>> If this problem is also in Linus's tree, I'd like to keep it in to keep > >>>> things "bug compatible". Please let me know what fix that I should > >>>> apply to resolve this. > >>> > >>> I am about to send out the patch that should fix this, so I will put you on cc. > >> > >> Not sure what happened here, but this patch is in 4.4-stable now, but > >> the fix is not. > > > > Because the fix came out _after_ I released that kernel? I can't go > > back in time... > > > > I kind of got the whole chronology thing. I am just surprised you > pulled only that patch (and not the fix) anyway, since you knew it > would break things, and that a fix was on the way. That way I knew you all would work quickly to get the fix in :) We do this all the time, nothing new here, being "bug compatible" is good... thanks, greg k-h