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 18:18:02 +0200 [thread overview]
Message-ID: <20140715161802.GB4775@pd.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F3285D02E@ORSMSX114.amr.corp.intel.com>
On Tue, Jul 15, 2014 at 03:57:42PM +0000, Luck, Tony wrote:
> Oops - not quite. We moved creation of the EDAC trace point into
> drivers/ras/ras.c and edac is not x86 specific.
>
> We also create the PCIe AER tracepoint there too - PCIe is not x86
> specific.
Right, but AFAIK, only x86 uses those. And frankly, we don't know
whether other arches would have interest in those or would like to grow
their own.
So, I don't have an idea whether we want to make the whole RAS stuff
arch-specific or we have to talk about it or we have to leave us that
option open and so on...
It is hard to say.
One example to mud the situation even more :-):
The APEI stuff is apparently being used by arm now too, but without the
NMI which is x86-specific. Carving that whole thing out took a bit of
work but it got done.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2014-07-15 16:18 UTC|newest]
Thread overview: 7+ 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
2014-07-15 15:57 ` Luck, Tony
2014-07-15 16:18 ` Borislav Petkov [this message]
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=20140715161802.GB4775@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox