From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Jan Beulich <jbeulich@suse.com>,
chegger@amazon.de, xen-devel@lists.xen.org
Cc: jinsong.liu@alibaba-inc.com
Subject: Re: [PATCH V3] x86, mce: Consolidate AMD mcheck initialization
Date: Thu, 29 May 2014 11:31:26 -0500 [thread overview]
Message-ID: <538760DE.5060503@amd.com> (raw)
In-Reply-To: <53876DC202000078000B52FA@mail.emea.novell.com>
On 5/29/2014 11:26 AM, Jan Beulich wrote:
>>>> Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com> 05/28/14 5:55 PM >>>
>> amd_k8.c did a lot of common work and very little K8
>> specific work. So merge init functions of amd_f10.c and
>> amd_k8.c and move it into the common amd_mcheck_init
>> handler. With that done, there is not much left in either
>> files, so fold all code into just one file - mce_amd.c
>>
>> While at it, update the comments regarding documentation
>> with correct URL's and revision numbers.
>>
>> Also, update copyright info.
>>
>> Changes in V2:
> >- Fix coding style issues
>> Changes in V3:
> >- More coding style fixes.
>> Signed-off-by: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
> Looks like you lost Christoph's ack - everything else looks fine now.
>
>
Yeah.was unsure of adding it just in case I missed something and had to
spin another patch.
Figured if everything is OK, then you could add it while committing :)
Thanks,
-Aravind.
next prev parent reply other threads:[~2014-05-29 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 15:52 [PATCH V3] x86, mce: Consolidate AMD mcheck initialization Aravind Gopalakrishnan
2014-05-29 16:26 ` Jan Beulich
2014-05-29 16:31 ` Aravind Gopalakrishnan [this message]
2014-05-30 6:33 ` Jan Beulich
2014-05-30 15:33 ` Aravind Gopalakrishnan
-- strict thread matches above, loose matches on Subject: below --
2014-05-28 15:51 Aravind Gopalakrishnan
2014-05-28 15:59 ` Aravind Gopalakrishnan
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=538760DE.5060503@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=chegger@amazon.de \
--cc=jbeulich@suse.com \
--cc=jinsong.liu@alibaba-inc.com \
--cc=xen-devel@lists.xen.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.