From: "Chen, Gong" <gong.chen@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>,
tony.luck@intel.com, naveen.n.rao@linux.vnet.ibm.com,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ACPI, APEI, GHES: Cleanup ghes codes for memory error handling
Date: Sat, 14 Dec 2013 08:42:43 -0500 [thread overview]
Message-ID: <20131214134243.GB2823@gchen.bj.intel.com> (raw)
In-Reply-To: <20131127021541.GA32135@gchen.bj.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
On Tue, Nov 26, 2013 at 09:15:42PM -0500, Chen, Gong wrote:
> Date: Tue, 26 Nov 2013 21:15:42 -0500
> From: "Chen, Gong" <gong.chen@linux.intel.com>
> To: Borislav Petkov <bp@alien8.de>
> Cc: tony.luck@intel.com, naveen.n.rao@linux.vnet.ibm.com,
> linux-acpi@vger.kernel.org
> Subject: Re: [PATCH v2 2/2] ACPI, APEI, GHES: Cleanup ghes codes for memory
> error handling
> User-Agent: Mutt/1.5.21 (2010-09-15)
>
> On Tue, Nov 26, 2013 at 08:23:35AM +0100, Borislav Petkov wrote:
> > Date: Tue, 26 Nov 2013 08:23:35 +0100
> > From: Borislav Petkov <bp@alien8.de>
> > To: "Chen, Gong" <gong.chen@linux.intel.com>
> > Cc: tony.luck@intel.com, naveen.n.rao@linux.vnet.ibm.com,
> > linux-acpi@vger.kernel.org
> > Subject: Re: [PATCH v2 2/2] ACPI, APEI, GHES: Cleanup ghes codes for memory
> > error handling
> > User-Agent: Mutt/1.5.21 (2010-09-15)
> >
> > On Tue, Nov 26, 2013 at 01:54:57AM -0500, Chen, Gong wrote:
> > > In this patch so-called cleanup includes an implied PFN check for UC
> > > error but missed in current codes.
> >
> > Right, I was about to look at it. You probably should add this to the
> > commit message so that it is clear.
> >
>
> How about this:
>
> Add proper PFN validity check for UC error and cleanup the code logic
> to make it simpler and cleaner.
>
> If OK and reasonable for this patch, would you mind helping to update the
> introduction in the patch before merging it?
Hi, Boris
Will you pick up this patch in your RAS request pull?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-14 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 7:15 [PATCH v2 1/2] ACPI, APEI, GHES: Remove strict check for memory error handling Chen, Gong
2013-11-25 7:15 ` [PATCH v2 2/2] ACPI, APEI, GHES: Cleanup ghes codes " Chen, Gong
2013-11-26 6:54 ` Chen, Gong
2013-11-26 7:23 ` Borislav Petkov
2013-11-27 2:15 ` Chen, Gong
2013-12-14 13:42 ` Chen, Gong [this message]
2013-11-26 9:04 ` Naveen N. Rao
2013-12-21 12:41 ` Borislav Petkov
2013-11-25 17:13 ` [PATCH v2 1/2] ACPI, APEI, GHES: Remove strict check " Borislav Petkov
2013-11-26 9:02 ` Naveen N. Rao
2013-11-26 9:31 ` Chen, Gong
2013-12-14 13:42 ` Chen, Gong
2013-12-16 14:51 ` Borislav Petkov
2013-12-16 14:40 ` Chen, Gong
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=20131214134243.GB2823@gchen.bj.intel.com \
--to=gong.chen@linux.intel.com \
--cc=bp@alien8.de \
--cc=linux-acpi@vger.kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--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 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.