From: Salil Mehta via <qemu-devel@nongnu.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "xianglai li" <lixianglai@loongson.cn>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Bernhard Beschow" <shentey@gmail.com>,
"Salil Mehta" <salil.mehta@opnsrc.net>,
"Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Song Gao" <gaosong@loongson.cn>,
"Igor Mammedov" <imammedo@redhat.com>,
"Ani Sinha" <anisinha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"wangyanan (Y)" <wangyanan55@huawei.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Bibo Mao" <maobibo@loongson.cn>
Subject: RE: [PATCH v3 2/7] Update CPUs AML with cpu-(ctrl)dev change
Date: Tue, 26 Sep 2023 15:52:48 +0000 [thread overview]
Message-ID: <726b4f44a38e4ee8b476ab6130e29b13@huawei.com> (raw)
In-Reply-To: <20230926080436-mutt-send-email-mst@kernel.org>
> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Tuesday, September 26, 2023 1:07 PM
> To: Salil Mehta <salil.mehta@huawei.com>
> Cc: xianglai li <lixianglai@loongson.cn>; qemu-devel@nongnu.org; Bernhard
> Beschow <shentey@gmail.com>; Salil Mehta <salil.mehta@opnsrc.net>; Xiaojuan
> Yang <yangxiaojuan@loongson.cn>; Song Gao <gaosong@loongson.cn>; Igor
> Mammedov <imammedo@redhat.com>; Ani Sinha <anisinha@redhat.com>; Paolo
> Bonzini <pbonzini@redhat.com>; Richard Henderson
> <richard.henderson@linaro.org>; Eduardo Habkost <eduardo@habkost.net>;
> Marcel Apfelbaum <marcel.apfelbaum@gmail.com>; Philippe Mathieu-Daudé
> <philmd@linaro.org>; wangyanan (Y) <wangyanan55@huawei.com>; Daniel P.
> Berrangé <berrange@redhat.com>; Peter Xu <peterx@redhat.com>; David
> Hildenbrand <david@redhat.com>; Bibo Mao <maobibo@loongson.cn>
> Subject: Re: [PATCH v3 2/7] Update CPUs AML with cpu-(ctrl)dev change
>
> On Tue, Sep 26, 2023 at 12:03:46PM +0000, Salil Mehta wrote:
> > Sure, ARM patch-set follows exactly above rules.
> >
>
>
> Almost.
>
> Co-developed-by: Salil Mehta <salil.mehta@huawei.com>
> Signed-off-by: Salil Mehta <salil.mehta@huawei.com>
> Co-developed-by: Keqian Zhu <zhukeqian1@huawei.com>
> Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com>
> Signed-off-by: Salil Mehta <salil.mehta@huawei.com>
>
> You should drop your own Co-developed-by as well as multiple Signed-off-by.
https://docs.kernel.org/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
Reference: Co-developed-by: Pasting excerpt from above link:
"1. Standard sign-off procedure applies, i.e. the ordering of
Signed-off-by: tags should reflect the chronological history
of the patch insofar as possible, regardless of whether the
author is attributed via From: or Co-developed-by:.
2.Notably, the last Signed-off-by: must always be that of the
developer submitting the patch."
To be able to achieve 1. I have to put Co-developed-by: of
mine at the top as I am the main author of the patch-set
historically and have been continually driving the work.
(It is a common rule even within the kernel to keep first
SOB that of the main author)
Reference: Signed-off-by: Excerpt from above link:
" Any further SoBs (Signed-off-by:'s) following the author's
SoB are from people handling and transporting the patch, but
were not involved in its development. SoB chains should
reflect the real route a patch took as it was propagated to
the maintainers and ultimately to Linus, with the first SoB
entry signalling primary authorship of a single author."
And since I am the person who is submitting the patches
(which might or not be the same in future) I need to put
my SOB in any case to be able to achieve 2.
This is to ensure primary author remains the first SOD/CDY.
Thanks
Salil.
next prev parent reply other threads:[~2023-09-26 15:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 9:54 [PATCH v3 0/7] *** Adds CPU hot-plug support to Loongarch *** xianglai li
2023-09-26 9:54 ` [PATCH v3 1/7] Update ACPI GED framework to support vcpu hot-(un)plug xianglai li
2023-09-26 10:50 ` Salil Mehta via
2023-09-26 12:16 ` lixianglai
2023-09-26 11:02 ` Michael S. Tsirkin
2023-09-26 11:26 ` lixianglai
2023-09-26 12:08 ` Michael S. Tsirkin
2023-09-26 12:38 ` Salil Mehta via
2023-09-27 15:18 ` Michael S. Tsirkin
2023-09-26 12:03 ` Michael S. Tsirkin
2023-09-26 9:54 ` [PATCH v3 2/7] Update CPUs AML with cpu-(ctrl)dev change xianglai li
2023-09-26 10:49 ` Salil Mehta via
2023-09-26 11:12 ` Michael S. Tsirkin
2023-09-26 11:45 ` Salil Mehta via
2023-09-26 11:54 ` Michael S. Tsirkin
2023-09-26 12:03 ` Salil Mehta via
2023-09-26 12:07 ` Michael S. Tsirkin
2023-09-26 15:52 ` Salil Mehta via [this message]
2023-09-26 17:38 ` Michael S. Tsirkin
2023-09-26 12:49 ` lixianglai
2023-09-27 15:17 ` Michael S. Tsirkin
2023-09-28 1:36 ` lixianglai
2023-09-26 12:30 ` Daniel P. Berrangé
2023-09-27 15:16 ` Michael S. Tsirkin
2023-09-26 12:17 ` lixianglai
2023-09-26 9:54 ` [PATCH v3 3/7] Added CPU topology support for Loongarch xianglai li
2023-09-26 9:54 ` [PATCH v3 4/7] Optimize loongarch_irq_init function implementation xianglai li
2023-09-26 9:54 ` [PATCH v3 5/7] Add basic CPU hot-(un)plug support for Loongarch xianglai li
2023-09-26 9:54 ` [PATCH v3 6/7] Add support of *unrealize* for Loongarch cpu xianglai li
2023-09-26 9:54 ` [PATCH v3 7/7] Update the ACPI table for the Loongarch CPU xianglai li
2023-09-26 10:58 ` Salil Mehta via
2023-09-27 2:26 ` lixianglai
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=726b4f44a38e4ee8b476ab6130e29b13@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=anisinha@redhat.com \
--cc=berrange@redhat.com \
--cc=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=gaosong@loongson.cn \
--cc=imammedo@redhat.com \
--cc=lixianglai@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=richard.henderson@linaro.org \
--cc=salil.mehta@huawei.com \
--cc=salil.mehta@opnsrc.net \
--cc=shentey@gmail.com \
--cc=wangyanan55@huawei.com \
--cc=yangxiaojuan@loongson.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;
as well as URLs for NNTP newsgroup(s).