All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	tony.luck@intel.com, bp@alien8.de, slaoub@gmail.com,
	luto@amacapital.net, x86@kernel.org,
	linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH] x86, mce, severities: Add AMD severities function
Date: Tue, 17 Mar 2015 08:42:14 +0100	[thread overview]
Message-ID: <20150317074214.GA27687@gmail.com> (raw)
In-Reply-To: <1426526164-3806-1-git-send-email-Aravind.Gopalakrishnan@amd.com>


* Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com> wrote:

> Add a severities function that caters to AMD processors.
> This allows us to do some vendor specific work within the
> function if necessary.
> 
> Also, introduce a vendor flag bitfield which contains vendor
> specific flags. The severities code uses this to define error
> scope based on the prescence of the flags field.

So it would be nice to see actual use of this new facility, within the 
same patch series?

Thanks,

	Ingo

  reply	other threads:[~2015-03-17  7:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 17:16 [PATCH] x86, mce, severities: Add AMD severities function Aravind Gopalakrishnan
2015-03-17  7:42 ` Ingo Molnar [this message]
2015-03-17  9:04   ` Borislav Petkov
2015-03-17 10:11     ` Ingo Molnar
2015-03-17 10:20 ` Borislav Petkov
2015-03-17 18:41   ` Aravind Gopalakrishnan
2015-03-17 18:44     ` Borislav Petkov
2015-03-19  0:01       ` Luck, Tony
2015-03-19  9:29         ` Borislav Petkov
2015-03-19 14:41           ` Aravind Gopalakrishnan
2015-03-19 15:53             ` Borislav Petkov
2015-03-19 16:20               ` Aravind Gopalakrishnan
2015-03-19 17:15                 ` Luck, Tony
2015-03-20 15:59                   ` Aravind Gopalakrishnan
2015-03-20 16:03                     ` Borislav Petkov
2015-03-20 17:49                       ` 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=20150317074214.GA27687@gmail.com \
    --to=mingo@kernel.org \
    --cc=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.