From: Borislav Petkov <bp@alien8.de>
To: "Chrzaniuk, Hubert" <hubert.chrzaniuk@intel.com>
Cc: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"dougthompson@xmission.com" <dougthompson@xmission.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"Anaczkowski, Lukasz" <lukasz.anaczkowski@intel.com>
Subject: Re: [PATCH 1/1] EDAC, sb_edac: Fix channel reporting on Knights Landing
Date: Wed, 3 Aug 2016 09:12:28 +0200 [thread overview]
Message-ID: <20160803071228.GC31099@nazgul.tnic> (raw)
In-Reply-To: <570CC49A75F8F64D9F711A9B9476C48C1FC2862E@IRSMSX101.ger.corp.intel.com>
On Wed, Aug 03, 2016 at 07:06:56AM +0000, Chrzaniuk, Hubert wrote:
> The original patch has been prepared by Lukas, then I [Hubert] rebased
> it, added commentary and cleaned up the code. In the end, Lukas
> modified it a bit once again according to suggestions from Tony. My
> SOB is unnecessary here, it only makes it more confusing.
So aspects like that can (and should!) be documented in the commit
message in free text, before the SOB chain. Something like this, for
example:
"...
Hubert:
- rebased to 4.8
- comments and code cleanup
"
You can send me just the exact free text you want in there as a reply to
this message and I'll integrate it.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2016-08-03 7:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 23:44 Lukasz Odzioba
2016-07-29 4:15 ` Odzioba, Lukasz
2016-08-03 6:44 ` Borislav Petkov
2016-08-03 7:06 ` Chrzaniuk, Hubert
2016-08-03 7:12 ` Borislav Petkov [this message]
2016-08-03 7:44 ` Chrzaniuk, Hubert
2016-08-03 7:58 ` Borislav Petkov
2016-08-03 8:54 ` Borislav Petkov
2016-08-03 9:25 ` Chrzaniuk, Hubert
2016-08-03 9:31 ` Borislav Petkov
2016-08-03 10:23 ` 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=20160803071228.GC31099@nazgul.tnic \
--to=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=hubert.chrzaniuk@intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.anaczkowski@intel.com \
--cc=lukasz.odzioba@intel.com \
--cc=mchehab@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®