From: Borislav Petkov <bp@alien8.de>
To: Hubert Chrzaniuk <hubert.chrzaniuk@intel.com>
Cc: lukasz.anaczkowski@intel.com, mchehab@osg.samsung.com,
dougthompson@xmission.com, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org, Jim Snow <jim.m.snow@intel.com>
Subject: Re: [PATCH 1/4] EDAC: add DDR4 flag
Date: Wed, 2 Dec 2015 20:28:00 +0100 [thread overview]
Message-ID: <20151202192759.GN3783@pd.tnic> (raw)
In-Reply-To: <1449070712-15177-2-git-send-email-hubert.chrzaniuk@intel.com>
On Wed, Dec 02, 2015 at 04:38:29PM +0100, Hubert Chrzaniuk wrote:
> From: Jim Snow <jim.m.snow@intel.com>
>
> Make EDAC aware of DDR4/RDDR4 mem types.
>
> Signed-off-by: Jim Snow <jim.m.snow@intel.com>
> Signed-off-by: Lukasz Anaczkowski <lukasz.anaczkowski@intel.com>
> Signed-off-by: Hubert Chrzaniuk <hubert.chrzaniuk@intel.com>
How am I to understand this SoB chain?
Jim wrote it, Lukasz did something to it and Hubert sends it?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2015-12-02 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 15:38 [PATCH 0/4] Xeon PHI Knights Landing support for EDAC module Hubert Chrzaniuk
2015-12-02 15:38 ` [PATCH 1/4] EDAC: add DDR4 flag Hubert Chrzaniuk
2015-12-02 19:28 ` Borislav Petkov [this message]
2015-12-03 7:51 ` Anaczkowski, Lukasz
2015-12-03 9:08 ` Borislav Petkov
2015-12-02 15:38 ` [PATCH 2/4] sb_edac: virtualize several hard-coded functions Hubert Chrzaniuk
2015-12-02 15:38 ` [PATCH 3/4] sb_edac: support for duplicate device IDs Hubert Chrzaniuk
2015-12-02 15:38 ` [PATCH 4/4] sb_edac: add Knights Landing (Xeon Phi gen 2) support Hubert Chrzaniuk
-- strict thread matches above, loose matches on Subject: below --
2015-12-03 9:48 [PATCH 0/4] Xeon PHI Knights Landing support for EDAC module Hubert Chrzaniuk
2015-12-03 9:48 ` [PATCH 1/4] EDAC: add DDR4 flag Hubert Chrzaniuk
2015-12-03 10:48 ` Borislav Petkov
2015-12-03 19:16 ` Luck, Tony
2015-12-03 19:43 ` Borislav Petkov
2015-12-03 21:53 ` Luck, Tony
2015-11-30 17:22 Chrzaniuk, Hubert
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=20151202192759.GN3783@pd.tnic \
--to=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=hubert.chrzaniuk@intel.com \
--cc=jim.m.snow@intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.anaczkowski@intel.com \
--cc=mchehab@osg.samsung.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