On Tue, Jan 06, 2015 at 04:23:58PM +0000, Ard Biesheuvel wrote: > On 6 January 2015 at 16:05, Will Deacon <will.deacon@xxxxxxx> wrote: > > On Tue, Jan 06, 2015 at 03:54:29PM +0000, Ard Biesheuvel wrote: > >> On 6 January 2015 at 15:52, Leif Lindholm <leif.lindholm@xxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
