From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Quan Nguyen <quan@os.amperecomputing.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org,
Open Source Submission <patches@amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
Thang Nguyen <thang@os.amperecomputing.com>
Subject: Re: [PATCH v2 2/2] misc: smpro-errmon: Add dimm training failure syndrome
Date: Fri, 10 Mar 2023 08:06:32 +0100 [thread overview]
Message-ID: <ZArW+JvLTLn796Wx@kroah.com> (raw)
In-Reply-To: <57a36c86-3d17-88fd-2ef1-ee4adcea1ce4@os.amperecomputing.com>
On Fri, Mar 10, 2023 at 07:20:56AM +0700, Quan Nguyen wrote:
>
>
> On 10/03/2023 00:05, Greg Kroah-Hartman wrote:
> > On Tue, Feb 28, 2023 at 04:20:10PM +0700, Quan Nguyen wrote:
> > > Adds event_dimm[0-15]_syndrome sysfs to report the failure syndrome
> > > to BMC when DIMM training failed.
> > >
> > > Signed-off-by: Quan Nguyen <quan@os.amperecomputing.com>
> > > ---
> > > v2:
> > > + Change "to initialized" to "to initialize" [Paul]
> > > + Corrected kernel version to 6.3 [Greg,Paul]
> >
> > Sorry, but this is going to have to be 6.4 now.
> >
>
> Thanks Greg for the review,
>
> So should I send another version for the patch with 6.3 to 6.4 correction ?
Yes please, for both, so I can queue them up now for the 6.4-rc1 merge
window.
thanks,
greg k-h
prev parent reply other threads:[~2023-03-10 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 9:20 [PATCH v2 0/2] Add DIMM 2x refresh event and failure syndrome Quan Nguyen
2023-02-28 9:20 ` [PATCH v2 1/2] misc: smpro-errmon: Add DIMM 2x Refresh rate event Quan Nguyen
2023-02-28 9:20 ` [PATCH v2 2/2] misc: smpro-errmon: Add dimm training failure syndrome Quan Nguyen
2023-03-09 17:05 ` Greg Kroah-Hartman
2023-03-10 0:20 ` Quan Nguyen
2023-03-10 7:06 ` Greg Kroah-Hartman [this message]
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=ZArW+JvLTLn796Wx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=pmenzel@molgen.mpg.de \
--cc=quan@os.amperecomputing.com \
--cc=thang@os.amperecomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox