All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
	<tony.luck@intel.com>, <slaoub@gmail.com>, <luto@amacapital.net>,
	<x86@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-edac@vger.kernel.org>
Subject: Re: [PATCH V3 1/2] x86, mce, severities: Add AMD severities function
Date: Tue, 24 Mar 2015 10:23:43 -0500	[thread overview]
Message-ID: <5511817F.2050905@amd.com> (raw)
In-Reply-To: <20150324151840.GB11525@pd.tnic>

On 3/24/2015 10:18 AM, Borislav Petkov wrote:
> On Tue, Mar 24, 2015 at 10:02:33AM -0500, Aravind Gopalakrishnan wrote:
>> I think the clean way to fix this would be to move the line to [patch 2/2].
>> Besides, we would need a new patch 2 anyway as the patch application would
>> fail due to changes to the comment line.
> Already done and done.
>
> Here's what I'm working with:
>
> http://git.kernel.org/cgit/linux/kernel/git/bp/bp.git/log/?h=tip-x86-ras
>

Ah. Ok, Thanks!

-Aravind.

  reply	other threads:[~2015-03-24 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 15:42 [PATCH V3 0/2] Rework mce_severity Aravind Gopalakrishnan
2015-03-23 15:42 ` [PATCH V3 1/2] x86, mce, severities: Add AMD severities function Aravind Gopalakrishnan
2015-03-24  8:30   ` Borislav Petkov
2015-03-24 15:02     ` Aravind Gopalakrishnan
2015-03-24 15:18       ` Borislav Petkov
2015-03-24 15:23         ` Aravind Gopalakrishnan [this message]
2015-03-24 16:03           ` Borislav Petkov
2015-03-23 15:42 ` [PATCH V3 2/2] x86, mce, severities: Define mce_severity function pointer Aravind Gopalakrishnan
2015-03-23 21:54 ` [PATCH V3 0/2] Rework mce_severity Luck, Tony

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=5511817F.2050905@amd.com \
    --to=aravind.gopalakrishnan@amd.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=slaoub@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.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.