From: Keir Fraser <keir@xensource.com>
To: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] small mca cleanup
Date: Thu, 16 Aug 2007 16:28:33 +0100 [thread overview]
Message-ID: <C2EA2BB1.144B0%keir@xensource.com> (raw)
In-Reply-To: <200708161714.37666.Christoph.Egger@amd.com>
Oh yeah, sure: Xen-specific stuff and the general MCE/MCA reworking that
you're talking about are one thing. But there's no point in minor fixes and
stylistic cleanups going into Xen and bypassing upstream Linux.
-- Keir
On 16/8/07 16:14, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> On Thursday 16 August 2007 16:42:37 Keir Fraser wrote:
>> The file you modify is from upstream Linux, and that's where this patch
>> belongs.
>
> oh, I have many changes in my queue in files that are from Linux
> (and also new files, that are not in Linux).
> They do one thing, that does not belong into Linux (or any other OS):
> Notifying guests, preferably Dom0.
>
> I'm about extracting the least intrusive changes first.
> We can still push changes into Linux that belong to there.
>
> For more information where this is going to, please see the
> discussion "MCE/MCA concept" on this list. The thread started here:
> http://lists.xensource.com/archives/html/xen-devel/2007-05/msg01015.html
>
> Christoph
>
>>
>> -- Keir
>>
>> On 16/8/07 15:36, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
>>> Hi!
>>>
>>> The MCG_CAP MSR never returns a negative count of available
>>> error-reporting banks. Thus make nr_mce_banks unsigned.
>>>
>>> While here, do some other minor cleanups.
>>>
>>> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
>
>
next prev parent reply other threads:[~2007-08-16 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 14:36 [PATCH] small mca cleanup Christoph Egger
2007-08-16 14:42 ` Keir Fraser
2007-08-16 15:14 ` Christoph Egger
2007-08-16 15:28 ` Keir Fraser [this message]
2007-08-16 16:06 ` Keir Fraser
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=C2EA2BB1.144B0%keir@xensource.com \
--to=keir@xensource.com \
--cc=Christoph.Egger@amd.com \
--cc=xen-devel@lists.xensource.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.