From: Peter Zijlstra <peterz@infradead.org>
To: jiang.biao2@zte.com.cn
Cc: chen.lin130@zte.com.cn, mingo@redhat.com,
linux-kernel@vger.kernel.org, zhong.weidong@zte.com.cn,
tan.hu@zte.com.cn.cn, cheng.lin130@zte.com.cn, tan.hu@zte.com.cn
Subject: Re: [PATCH] sched/numa: do not balance tasks onto isolated cpus
Date: Tue, 24 Jul 2018 11:06:51 +0200 [thread overview]
Message-ID: <20180724090651.GK2494@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <201807240911372861670@zte.com.cn>
On Tue, Jul 24, 2018 at 09:11:37AM +0800, jiang.biao2@zte.com.cn wrote:
> >> Signed-off-by: Cheng Lin <cheng.lin130@zte.com.cn>
> >> Signed-off-by: Tan Hu <tan.hu@zte.com.cn>
> >> Signed-off-by: Jiang Biao <jiang.biao2@zte.com.cn>
> >
> >This SoB chain is invalid.
> Mm, we don't quite understand what the *Signed-off-by* precisely means,
> Does it only mean DCO(developer certificate of origin)?
> As we understood, multiple SoBs could be used to indicate co-authors.
> If SoB only means DCO, how can the patches reflect co-authors?
It specifically does not allow for co-authorship. I think there's a
Co-Authored-by: tag invented by some people (check the git logs) but
especially for such a dinky little patch, I wouldn't bother. Maybe have
your co-workers review the patch or something.
next prev parent reply other threads:[~2018-07-24 9:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 5:39 Chen Lin
2018-07-23 8:40 ` Peter Zijlstra
2018-07-24 1:11 ` jiang.biao2
2018-07-24 9:06 ` Peter Zijlstra [this message]
2018-07-25 0:30 ` jiang.biao2
2018-07-25 8:35 ` Peter Zijlstra
2018-07-25 8:52 ` jiang.biao2
2018-07-23 20:06 ` kbuild test robot
2018-07-23 20:06 ` kbuild test robot
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=20180724090651.GK2494@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=chen.lin130@zte.com.cn \
--cc=cheng.lin130@zte.com.cn \
--cc=jiang.biao2@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tan.hu@zte.com.cn \
--cc=tan.hu@zte.com.cn.cn \
--cc=zhong.weidong@zte.com.cn \
/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
Powered by JetHome