From mboxrd@z Thu Jan 1 00:00:00 1970 From: Will Deacon Subject: Re: [PATCH v2 0/2] arm64: don't call early_*map() post paging_init() Date: Tue, 6 Jan 2015 19:18:34 +0000 Message-ID: <20150106191833.GD32449@arm.com> References: <1420551673-31416-1-git-send-email-leif.lindholm@linaro.org> <20150106135941.GA3484@arm.com> <20150106155208.GC3827@bivouac.eciton.net> <20150106160511.GD3484@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Ard Biesheuvel Cc: Leif Lindholm , "msalter-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Catalin Marinas List-Id: linux-efi@vger.kernel.org On Tue, Jan 06, 2015 at 04:23:58PM +0000, Ard Biesheuvel wrote: > On 6 January 2015 at 16:05, Will Deacon wrote: > > On Tue, Jan 06, 2015 at 03:54:29PM +0000, Ard Biesheuvel wrote: > >> On 6 January 2015 at 15:52, Leif Lindholm wrote: > >> > On Tue, Jan 06, 2015 at 02:04:50PM +0000, Ard Biesheuvel wrote: > >> >> >> Changes since v1: > >> >> >> - Rebased to v3.19-rc3 > >> >> >> - Added 'Fixes:' tags > >> >> >> - Reworked 1/2 to restore call to efi_setup_idmap() to the original > >> >> >> location in the boot process. > >> >> > > >> >> > Looks reasonable to me; do they need a CC stable, > >> >> > >> >> Yes, but with a note that both patches should be taken and the order > >> >> is retained, or we break bisect. > >> > > >> > Where would one add such a note? > >> > > >> > >> I guess the best way would be to not add a 'Cc: stable' tag, but send > >> an email to Greg once the patches have been merged by Linus. > > > > I thought Greg didn't take anything until it had hit mainline anyway? I > > think it should be fine with just the Cc... > > > > I know he doesn't, but do you know for a fact that he always takes > patches in the same order they appear in mainline? It would seem like > the reasonable thing to do, I guess, but we just have to make sure. If we really want to make sure we could either fold the two patches into one or add a dependency without a corresponding sha. I don't like waiting until they've hit mainline, because I'm sure that I'll forget! Will From mboxrd@z Thu Jan 1 00:00:00 1970 From: will.deacon@arm.com (Will Deacon) Date: Tue, 6 Jan 2015 19:18:34 +0000 Subject: [PATCH v2 0/2] arm64: don't call early_*map() post paging_init() In-Reply-To: References: <1420551673-31416-1-git-send-email-leif.lindholm@linaro.org> <20150106135941.GA3484@arm.com> <20150106155208.GC3827@bivouac.eciton.net> <20150106160511.GD3484@arm.com> Message-ID: <20150106191833.GD32449@arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Jan 06, 2015 at 04:23:58PM +0000, Ard Biesheuvel wrote: > On 6 January 2015 at 16:05, Will Deacon wrote: > > On Tue, Jan 06, 2015 at 03:54:29PM +0000, Ard Biesheuvel wrote: > >> On 6 January 2015 at 15:52, Leif Lindholm wrote: > >> > On Tue, Jan 06, 2015 at 02:04:50PM +0000, Ard Biesheuvel wrote: > >> >> >> Changes since v1: > >> >> >> - Rebased to v3.19-rc3 > >> >> >> - Added 'Fixes:' tags > >> >> >> - Reworked 1/2 to restore call to efi_setup_idmap() to the original > >> >> >> location in the boot process. > >> >> > > >> >> > Looks reasonable to me; do they need a CC stable, > >> >> > >> >> Yes, but with a note that both patches should be taken and the order > >> >> is retained, or we break bisect. > >> > > >> > Where would one add such a note? > >> > > >> > >> I guess the best way would be to not add a 'Cc: stable' tag, but send > >> an email to Greg once the patches have been merged by Linus. > > > > I thought Greg didn't take anything until it had hit mainline anyway? I > > think it should be fine with just the Cc... > > > > I know he doesn't, but do you know for a fact that he always takes > patches in the same order they appear in mainline? It would seem like > the reasonable thing to do, I guess, but we just have to make sure. If we really want to make sure we could either fold the two patches into one or add a dependency without a corresponding sha. I don't like waiting until they've hit mainline, because I'm sure that I'll forget! Will