[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131027110148.GA24817@pd.tnic>
Date: Sun, 27 Oct 2013 12:01:48 +0100
From: Borislav Petkov <bp@...en8.de>
To: Ingo Molnar <mingo@...nel.org>
Cc: Tony Luck <tony.luck@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
X86-ML <x86@...nel.org>, Matt Fleming <matt@...sole-pimps.org>
Subject: Re: [GIT PULLv2] For x86/mce ... enhanced error logs
On Sun, Oct 27, 2013 at 08:00:35AM +0100, Ingo Molnar wrote:
>
> * Tony Luck <tony.luck@...il.com> wrote:
>
> > > Hm, I'm not sure we should move something named after a hardware
> > > feature into lib/. It's not really generic C library functionality,
> >
> >
> > Not a hardware feature. CPER stands for Common Platform Error Record
> > from the UEFI standard. [...]
>
> By all means UEFI can be considered platform dependent at the moment:
>
> comet:~/tip> git grep -i uefi arch/arm/
> comet:~/tip> git grep -i uefi arch/arm64/
> comet:~/tip> git grep -i uefi arch/powerpc/
> comet:~/tip> git grep -i uefi arch/mips/
> comet:~/tip>
>
> If a committee says that a name of some standard is 'common platform' does
> not make it so. lib/ is mostly kept for mathematical, C-library alike
> functionality you see in CS textbooks.
>
> > As Chen Gong points out, drivers/acpi isn't the right place ... so if
> > not lib/ ... then where?
>
> drivers/uefi/?
Hmm, we do have drivers/firmware/, even drivers/firmware/efi/ subdir and
since this thing is part of the UEFI spec, we probably should stick it
there...
Matt, heads up^^^.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
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