Re: [GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-27 Thread Matt Fleming
On Sun, 27 Oct, at 09:34:09PM, Borislav Petkov wrote: > On Sun, Oct 27, 2013 at 08:22:15PM +, 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

Re: [GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-27 Thread Borislav Petkov
On Sun, Oct 27, 2013 at 08:22:15PM +, 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?e

Re: [GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-27 Thread Matt Fleming
On Sun, 27 Oct, at 12:01:48PM, Borislav Petkov wrote: > On Sun, Oct 27, 2013 at 08:00:35AM +0100, Ingo Molnar wrote: > > > > * Tony Luck 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

Re: [GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-27 Thread Borislav Petkov
On Sun, Oct 27, 2013 at 08:00:35AM +0100, Ingo Molnar wrote: > > * Tony Luck 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 Plat

Re: [GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-27 Thread Ingo Molnar
* Tony Luck 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

Re: [GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-26 Thread Christoph Hellwig
On Sat, Oct 26, 2013 at 02:34:52PM -0700, Tony Luck wrote: > As Chen Gong points out, drivers/acpi isn't the right place ... so if not > lib/ ... then where? A to be created drivers/efi? There should be a lot more shared EFI code coming sooner or later, shouldn't it? -- To unsubscribe from this

Re: [GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-26 Thread Tony Luck
> 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. So applicable to three? architectures. As Chen Gong points ou

Re: [GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-26 Thread Ingo Molnar
* Tony Luck wrote: > On Wed, Oct 23, 2013 at 10:42 AM, Luck, Tony wrote: > > Replacement for yesterday's pull request - fixes a build bug when > > CONFIG_SMP=n > > found by Fengguang's zero-day auto-build robot army. If you pulled (and > > pushed) > > that one before finding this in your mai

Re: [GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-26 Thread Ingo Molnar
* Luck, Tony wrote: > Replacement for yesterday's pull request - fixes a build bug when CONFIG_SMP=n > found by Fengguang's zero-day auto-build robot army. If you pulled (and > pushed) > that one before finding this in your mailbox - then I can send the one-line > patch to be applied on top of

Re: [GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-23 Thread Tony Luck
On Wed, Oct 23, 2013 at 10:42 AM, Luck, Tony wrote: > Replacement for yesterday's pull request - fixes a build bug when CONFIG_SMP=n > found by Fengguang's zero-day auto-build robot army. If you pulled (and > pushed) > that one before finding this in your mailbox - then I can send the one-line >

[GIT PULLv2] For x86/mce ... enhanced error logs

2013-10-23 Thread Luck, Tony
Replacement for yesterday's pull request - fixes a build bug when CONFIG_SMP=n found by Fengguang's zero-day auto-build robot army. If you pulled (and pushed) that one before finding this in your mailbox - then I can send the one-line patch to be applied on top of yesterday's version. -Tony The