linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Chao Fan <fanc.fnst@cn.fujitsu.com>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<peterz@infradead.org>, <akpm@linux-foundation.org>,
	<izumi.taku@jp.fujitsu.com>, Cao Jin <caoj.fnst@cn.fujitsu.com>
Subject: Re: [PATCH] Change the document about iowait
Date: Sat, 19 Nov 2016 10:39:16 -0700	[thread overview]
Message-ID: <20161119103916.3a562069@lwn.net> (raw)
In-Reply-To: <20161114034241.GA16830@localhost.localdomain>

On Mon, 14 Nov 2016 11:42:41 +0800
Chao Fan <fanc.fnst@cn.fujitsu.com> wrote:

> >Sorry for the delay on this.  Life has been...challenging...
> >  
> >> Signed-off-by: Cao Jin <caoj.fnst@cn.fujitsu.com>
> >> Signed-off-by: Chao Fan <fanc.fnst@cn.fujitsu.com>  
> >
> >What does this signoff chain mean?    
> 
> Hi jon,
> 
> I made this patch. He is my colleague who helped me a lot on
> investigating why this value decrease, so I added his s-o-b.
> I didn't know how to put the position, but both of us are
> responsible for this patch. Should I change and resend it?

The meaning of Signed-off-by is defined in the DOC, as seen in
Documentation/submitting-patches.rst.  In this case, the better approach
would have been to credit Cao Jin in the changelog, since he didn't write
the patch.

For a little documentation tweak like this it's not that big a deal,
though, so I simply gone ahead and applied it.

Thanks,

jon

      reply	other threads:[~2016-11-19 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26  2:41 [PATCH] Change the document about iowait Chao Fan
2016-11-09  1:33 ` Chao Fan
2016-11-13 15:47 ` Jonathan Corbet
2016-11-14  3:42   ` Chao Fan
2016-11-19 17:39     ` Jonathan Corbet [this message]

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=20161119103916.3a562069@lwn.net \
    --to=corbet@lwn.net \
    --cc=akpm@linux-foundation.org \
    --cc=caoj.fnst@cn.fujitsu.com \
    --cc=fanc.fnst@cn.fujitsu.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@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 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).