[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160209140701.GD26641@gmail.com>
Date: Tue, 9 Feb 2016 15:07:01 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Matt Fleming <matt@...eblueprint.co.uk>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Robert Elliott <elliott@....com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: linux-next: manual merge of the akpm tree with the tip tree
* Matt Fleming <matt@...eblueprint.co.uk> wrote:
> On Tue, 09 Feb, at 03:50:24PM, Stephen Rothwell wrote:
> > Hi Andrew,
> >
> > Today's linux-next merge of the akpm tree got a conflict in:
> >
> > arch/x86/platform/efi/efi.c
> >
> > between commit:
> >
> > 1e82b9479070 ("x86/efi: Show actual ending addresses in efi_print_memmap")
> >
> > from the tip tree and commit:
> >
> > e0532ef9f825 ("x86/efi: print size and base in binary units in efi_print_memmap")
> >
> > from the akpm tree.
> >
> > I fixed it up (see below) and can carry the fix as necessary (no action
> > is required).
>
> I think Andrew agreed to drop this patch from his tree,
>
> https://lkml.kernel.org/r/20160122151100.GA3747@codeblueprint.co.uk
... and I tried to follow up on the original submission to still preserve this
change, as it's no doubt useful to produce easier to read bootup messages.
Thanks,
Ingo
Powered by blists - more mailing lists