linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	oss-drivers@corigine.com
Subject: Re: [PATCH] docs: arm: tcm: Fix typo in description of TCM and MMU usage
Date: Thu, 9 Jun 2022 19:54:34 +0200	[thread overview]
Message-ID: <YqIz2uuEEU/YYIjG@corigine.com> (raw)
In-Reply-To: <877d5p4ui0.fsf@meer.lwn.net>

On Thu, Jun 09, 2022 at 11:27:51AM -0600, Jonathan Corbet wrote:
> Simon Horman <simon.horman@corigine.com> writes:
> 
> > On Thu, Jun 09, 2022 at 10:01:01AM -0600, Jonathan Corbet wrote:
> >> Simon Horman <simon.horman@corigine.com> writes:
> >> 
> >> > Correct a typo in the description of interaction between
> >> > the TCM and MMU.
> >> >
> >> > Found by inspection.
> >> >
> >> > Signed-off-by: Louis Peens <louis.peens@corigine.com>
> >> > Signed-off-by: Simon Horman <simon.horman@corigine.com>
> >> 
> >> Here too I have to ask: what does this signoff chain mean?  If two
> >> developers were needed for a single-character typo fix, then a
> >> Co-developed-by line is appropriate.  If you are forwarding a patch from
> >> Louis, then a From: line to get the authorship right is indicated ... ?
> >
> > The patch was created by me.
> >
> > Due to internal processes a release by a colleague is provided, that is the
> > purpose of Louis's sign off (overkill in this case, I agree).
> >
> > If Louis's sign-off is not necessary from your perspective then I'm happy
> > for you to drop it or for my to repost the patch without it.
> 
> So are you perhaps using it like a Reviewed-by?  If so, that's the tag
> that should be used.  But Signed-off-by has a well-defined meaning
> described by the DCO, and "release by a colleague" isn't in there, so
> I think that tag is not appropriate in this patch.

Thanks Jon,

I'll post a v2 without the tag in question.

Kind regards,
Simon

  reply	other threads:[~2022-06-09 17:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 11:27 [PATCH] docs: arm: tcm: Fix typo in description of TCM and MMU usage Simon Horman
2022-06-09 16:01 ` Jonathan Corbet
2022-06-09 16:44   ` Simon Horman
2022-06-09 17:27     ` Jonathan Corbet
2022-06-09 17:54       ` Simon Horman [this message]
2022-06-09 18:26         ` Jonathan Corbet

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=YqIz2uuEEU/YYIjG@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=corbet@lwn.net \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=oss-drivers@corigine.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;
as well as URLs for NNTP newsgroup(s).