From: Borislav Petkov <bp@alien8.de>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Vishal Verma <vishal.l.verma@intel.com>,
linux-nvdimm@lists.01.org, Tony Luck <tony.luck@intel.com>,
linux-edac@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>
Subject: [v3,1/2] nfit, mce: only handle uncorrectable machine checks
Date: Wed, 20 Feb 2019 20:39:40 +0100 [thread overview]
Message-ID: <20190220193939.GG3447@zn.tnic> (raw)
On Wed, Feb 20, 2019 at 02:26:45PM -0500, Jeff Moyer wrote:
> Sure, thanks for the quick reply, Boris! Also, thanks for your detailed
> commit messages. They really help with understanding the code changes.
Ha!
From now on I'll be showing that to *anyone* who complains when I ask of
them to make their commit messages understandable!
:-)
Thanks!
next reply other threads:[~2019-02-20 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 19:39 Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-21 17:09 [v3,1/2] nfit, mce: only handle uncorrectable machine checks Borislav Petkov
2019-02-21 16:11 Jeff Moyer
2019-02-20 19:47 Borislav Petkov
2019-02-20 19:40 Dan Williams
2019-02-20 19:26 Jeff Moyer
2019-02-20 19:18 Borislav Petkov
2019-02-20 18:59 Jeff Moyer
2018-10-26 0:37 Vishal Verma
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=20190220193939.GG3447@zn.tnic \
--to=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=jmoyer@redhat.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=tony.luck@intel.com \
--cc=vishal.l.verma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox