From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751241AbcCLFz5 (ORCPT ); Sat, 12 Mar 2016 00:55:57 -0500 Received: from mail-pf0-f174.google.com ([209.85.192.174]:35947 "EHLO mail-pf0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750746AbcCLFzs convert rfc822-to-8bit (ORCPT ); Sat, 12 Mar 2016 00:55:48 -0500 References: <20160308000315.294406921@linuxfoundation.org> <20160308000316.386547682@linuxfoundation.org> <20160308134401.GA25309@kroah.com> <20160312055040.GB20808@kroah.com> Mime-Version: 1.0 (1.0) In-Reply-To: <20160312055040.GB20808@kroah.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8BIT Message-Id: <3BE88637-7CEF-4445-9CF0-5FCCB97507BE@linaro.org> Cc: "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , Will Deacon X-Mailer: iPhone Mail (13D15) From: Ard Biesheuvel Subject: Re: [PATCH 4.4 34/74] arm64: vmemmap: use virtual projection of linear region Date: Sat, 12 Mar 2016 13:55:44 +0800 To: Greg Kroah-Hartman Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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.