From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv8 1/4] EDAC, altera: Add Altera L2 Cache and OCRAM EDAC Support
Date: Fri, 22 Jan 2016 19:08:30 +0100 [thread overview]
Message-ID: <20160122180830.GH9806@pd.tnic> (raw)
In-Reply-To: <56A25F59.5070306@mentor.com>
On Fri, Jan 22, 2016 at 06:56:57PM +0200, Vladimir Zapolskiy wrote:
> it sounds like the author of the original change is Dinh, but if you agreed
> about authorship transfer, then "From: Thor Thayer" statement should be
> correct, but in any case your SoB should follow Dinh's SoB, if you decide to
> keep the latter one.
>
> This consideration may apply to the other changes in the changeset as well.
So the patch author should be in the From:
If Thor has changed the original patch considerably, then you Thor and
Dinh could decide amongst each other who should be the author.
If Thor becomes the author and lands in From:, then the commit message
could state something like "based on original work from Dinh" or
"Originally-from: Dinh" and so on. "git log" has some examples.
The SOB chain shows who handled the patch on its way upstream. So in
this case, it should be:
SOB: Dinh (if From: is Dinh - otherwise Originally-by:)
SOB: Thor
SOB: Boris
if I'm going to pick it up and send it to Linus.
Ok?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
tthayer@opensource.altera.com
Cc: dougthompson@xmission.com, m.chehab@samsung.com,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, dinguyen@opensource.altera.com,
grant.likely@linaro.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, tthayer.linux@gmail.com
Subject: Re: [PATCHv8 1/4] EDAC, altera: Add Altera L2 Cache and OCRAM EDAC Support
Date: Fri, 22 Jan 2016 19:08:30 +0100 [thread overview]
Message-ID: <20160122180830.GH9806@pd.tnic> (raw)
In-Reply-To: <56A25F59.5070306@mentor.com>
On Fri, Jan 22, 2016 at 06:56:57PM +0200, Vladimir Zapolskiy wrote:
> it sounds like the author of the original change is Dinh, but if you agreed
> about authorship transfer, then "From: Thor Thayer" statement should be
> correct, but in any case your SoB should follow Dinh's SoB, if you decide to
> keep the latter one.
>
> This consideration may apply to the other changes in the changeset as well.
So the patch author should be in the From:
If Thor has changed the original patch considerably, then you Thor and
Dinh could decide amongst each other who should be the author.
If Thor becomes the author and lands in From:, then the commit message
could state something like "based on original work from Dinh" or
"Originally-from: Dinh" and so on. "git log" has some examples.
The SOB chain shows who handled the patch on its way upstream. So in
this case, it should be:
SOB: Dinh (if From: is Dinh - otherwise Originally-by:)
SOB: Thor
SOB: Boris
if I'm going to pick it up and send it to Linus.
Ok?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-01-22 18:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 17:34 [PATCHv8 1/4] EDAC, altera: Add Altera L2 Cache and OCRAM EDAC Support tthayer at opensource.altera.com
2016-01-21 17:34 ` tthayer
2016-01-21 17:34 ` tthayer
2016-01-21 17:34 ` [PATCHv8 2/4] ARM: dts: Add Altera L2 Cache and OCRAM EDAC entries tthayer at opensource.altera.com
2016-01-21 17:34 ` tthayer
2016-01-21 17:34 ` tthayer
2016-01-23 2:35 ` Rob Herring
2016-01-23 2:35 ` Rob Herring
2016-01-25 15:42 ` Thor Thayer
2016-01-25 15:42 ` Thor Thayer
2016-01-25 15:42 ` Thor Thayer
2016-01-21 17:34 ` [PATCHv8 3/4] ARM: socfpga: enable L2 cache ECC on startup tthayer at opensource.altera.com
2016-01-21 17:34 ` tthayer
2016-01-21 17:34 ` tthayer
2016-01-21 17:34 ` [PATCHv8 4/4] ARM: socfpga: Enable OCRAM " tthayer at opensource.altera.com
2016-01-21 17:34 ` tthayer
2016-01-21 17:34 ` tthayer
2016-01-22 6:02 ` [PATCHv8 1/4] EDAC, altera: Add Altera L2 Cache and OCRAM EDAC Support Vladimir Zapolskiy
2016-01-22 6:02 ` Vladimir Zapolskiy
2016-01-22 6:02 ` Vladimir Zapolskiy
2016-01-22 15:35 ` Thor Thayer
2016-01-22 15:35 ` Thor Thayer
2016-01-22 15:35 ` Thor Thayer
2016-01-22 16:56 ` Vladimir Zapolskiy
2016-01-22 16:56 ` Vladimir Zapolskiy
2016-01-22 16:56 ` Vladimir Zapolskiy
2016-01-22 18:08 ` Borislav Petkov [this message]
2016-01-22 18:08 ` Borislav Petkov
2016-01-22 22:05 ` Thor Thayer
2016-01-22 22:05 ` Thor Thayer
2016-01-22 22:05 ` Thor Thayer
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=20160122180830.GH9806@pd.tnic \
--to=bp@alien8.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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.