From: Borislav Petkov <bp@alien8.de>
To: Matt Fleming <matt@console-pimps.org>
Cc: Ingo Molnar <mingo@kernel.org>, Tony Luck <tony.luck@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86-ML <x86@kernel.org>
Subject: Re: [GIT PULLv2] For x86/mce ... enhanced error logs
Date: Sun, 27 Oct 2013 21:34:09 +0100 [thread overview]
Message-ID: <20131027203409.GC24817@pd.tnic> (raw)
In-Reply-To: <20131027202215.GD1982@console-pimps.org>
On Sun, Oct 27, 2013 at 08:22:15PM +0000, Matt Fleming wrote:
> I've certainly no problem with moving it under drivers/firmware/efi/,
> but please don't create a new subdirectory in drivers/ just for this.
Yeah, no - we have an subdir for this - drivers/firmware/efi/ so no need
for the drivers/u?efi thing.
My train of thought here is, we want to put all firmware-related crap
into drivers/firmware/ and since CPER is from the UEFI spec, it should
go into drivers/firmware/efi.
I guess we can apply that same logic to the remaining UEFI sh*tstorm
coming our way.
:-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-10-27 20:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 17:56 [GIT PULL] For x86/mce ... enhanced error logs Luck, Tony
2013-10-23 17:42 ` [GIT PULLv2] " Luck, Tony
2013-10-23 18:13 ` Tony Luck
2013-10-26 10:10 ` Ingo Molnar
2013-10-26 21:34 ` Tony Luck
2013-10-26 21:36 ` Christoph Hellwig
2013-10-27 7:00 ` Ingo Molnar
2013-10-27 11:01 ` Borislav Petkov
2013-10-27 20:22 ` Matt Fleming
2013-10-27 20:34 ` Borislav Petkov [this message]
2013-10-27 20:46 ` Matt Fleming
2013-10-28 18:53 ` [PATCH] Move cper.c from drivers/acpi/apei to drivers/firmware/efi Luck, Tony
2013-10-28 20:35 ` Matt Fleming
2013-10-29 8:16 ` Ingo Molnar
2013-10-26 10:06 ` [GIT PULLv2] For x86/mce ... enhanced error logs Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131027203409.GC24817@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mingo@kernel.org \
--cc=tony.luck@gmail.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.