[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140102103549.GC2618@console-pimps.org>
Date: Thu, 2 Jan 2014 10:35:49 +0000
From: Matt Fleming <matt@...sole-pimps.org>
To: Dave Young <dyoung@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org,
x86@...nel.org, mjg59@...f.ucam.org, hpa@...or.com,
James.Bottomley@...senPartnership.com, vgoyal@...hat.com,
ebiederm@...ssion.com, horms@...ge.net.au,
kexec@...ts.infradead.org, bp@...en8.de, greg@...ah.com,
toshi.kani@...com, akpm@...ux-foundation.org, mingo@...nel.org,
msalter@...hat.com, leif.lindholm@...aro.org
Subject: Re: [PATCH v7 00/12] kexec kernel efi runtime support
On Thu, 02 Jan, at 10:42:56AM, Dave Young wrote:
>
> Hi, Matt
>
> randconfig build robot reports several problems:
> 1. sparse warnings which should be fixed by the early_memremap patches
Yeah, this will be fixed up when Mark's memremap patch series gets
merged.
> Here is the fix for 2. and 3, please take a look. I'm not sure if I
> should resend the patches or leave them to you.
Please send these as separate patches and include the compiler errors in
the commit message. I'll pick them up and send them to Peter.
> build fix: move parse_efi_setup to efi*.c, call it in efi_init instead in setup.c
Why have you moved the call site for parse_efi_setup()? What's the
rationale? Parsing SETUP_* entries outside of parse_setup_data() seems
to me to be a step backwards in terms of clarity.
--
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists