From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Greg KH <greg@kroah.com>, Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>,
"Chen, Gong" <gong.chen@linux.intel.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andreas Noever <andreas.noever@gmail.com>
Subject: Re: linux-next: manual merge of the char-misc tree with the ia64 tree
Date: Tue, 15 Jul 2014 17:36:13 +0200 [thread overview]
Message-ID: <20140715153613.GA4775@pd.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F3285CF7A@ORSMSX114.amr.corp.intel.com>
On Tue, Jul 15, 2014 at 03:22:31PM +0000, Luck, Tony wrote:
> > Wait, do we really need a drivers/ras directory for one single driver?
> > Why not put it in drivers/misc/ instead? A whole subdir at the top of
> > drivers seems overkill and odd.
> >
> > As it's a memory driver, what about drivers/firmware/ or drivers/edac/
> > or drivers/platform?
>
> It isn't really a firmware driver, and definitely not an EDAC driver.
>
> drivers/platform/x86 seems at least plausible.
>
> Adding Boris as drivers/ras was his idea. I think he has plans
> for more stuff to go here.
Actually what I'd really like is to have a separate RAS subsystem where
we pull in all things RAS. Possibly arch-independent as I'm assuming
other arches would need RAS functionality at some point too.
Currently, all the stuff we're doing is x86-only so arch/x86/ras/ might
be a good place too, if other arches wanna do their own thing or if x86
RAS facilities turn out to be PITA to make arch-independent.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-07-15 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 6:43 linux-next: manual merge of the char-misc tree with the ia64 tree Stephen Rothwell
2014-07-15 13:44 ` Greg KH
2014-07-15 13:49 ` Greg KH
2014-07-15 15:22 ` Luck, Tony
2014-07-15 15:36 ` Borislav Petkov [this message]
2014-07-15 15:57 ` Luck, Tony
2014-07-15 15:57 ` Luck, Tony
2014-07-15 16:18 ` Borislav Petkov
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=20140715153613.GA4775@pd.tnic \
--to=bp@alien8.de \
--cc=andreas.noever@gmail.com \
--cc=arnd@arndb.de \
--cc=gong.chen@linux.intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.com \
/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.