From: "zhao1.liu@intel.com" <zhao1.liu@intel.com>
To: "Wangxin (Alexander)" <wangxinxin.wang@huawei.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Wang Xin via <qemu-devel@nongnu.org>,
"Huangweidong (C)" <weidong.huang@huawei.com>,
xietuo <xietuo@huawei.com>
Subject: Re: [PATCH] target/i386: Add support save/load exception error_code
Date: Wed, 20 Aug 2025 18:16:05 +0800 [thread overview]
Message-ID: <aKWgZRwKpAx+3o3h@intel.com> (raw)
In-Reply-To: <e4018c7b70ef4d81bafcc7395551e735@huawei.com>
On Wed, Aug 20, 2025 at 02:18:21AM +0000, Wangxin (Alexander) wrote:
> Date: Wed, 20 Aug 2025 02:18:21 +0000
> From: "Wangxin (Alexander)" <wangxinxin.wang@huawei.com>
> Subject: RE: [PATCH] target/i386: Add support save/load exception error_code
>
> >
> > Queued, thanks. But please let me know what's the correct signed off by chain;
> > either Tuo created the patch, and then you should have "--author" for him and
> > his SoB first; or you did, and then Tuo's SoB is unnecessary.
> >
> > Paolo
> >
>
> The author is me,
But if Tuo co-worked with you, his SoB is also necessary to keep:
"git commits will usually be expected to have a ``Signed-off-by``
line for each contributor involved in creation of the patch."
In this case, “Co-developed-by” is not necessary for now.
I think the reason of confusion is, as the person sending the patch,
you'd have put your SoB on the last line.
Thanks,
Zhao
next prev parent reply other threads:[~2025-08-20 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 14:58 [PATCH] target/i386: Add support save/load exception error_code Wang Xin via
2025-08-19 15:28 ` Paolo Bonzini
2025-08-20 2:18 ` Wangxin (Alexander) via
2025-08-20 10:16 ` zhao1.liu [this message]
2025-08-20 10:05 ` Zhao Liu
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=aKWgZRwKpAx+3o3h@intel.com \
--to=zhao1.liu@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.com \
--cc=xietuo@huawei.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 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.