From: gengdongjiu <gengdongjiu@huawei.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: peter.maydell@linaro.org, ehabkost@redhat.com,
kvm@vger.kernel.org, imammedo@redhat.com, pbonzini@redhat.com,
mtosatti@redhat.com, qemu-devel@nongnu.org, linuxarm@huawei.com,
shannon.zhaosl@gmail.com, Xiang Zheng <zhengxiang9@huawei.com>,
qemu-arm@nongnu.org, james.morse@arm.com, xuwei5@huawei.com,
jonathan.cameron@huawei.com, wanghaibin.wang@huawei.com,
lersek@redhat.com, rth@twiddle.net
Subject: Re: [PATCH v20 0/5] Add ARMv8 RAS virtualization support in QEMU
Date: Mon, 28 Oct 2019 23:10:46 +0800 [thread overview]
Message-ID: <a16f00df-98cd-3469-1c64-d9d7a6ccaccf@huawei.com> (raw)
In-Reply-To: <20191028104834-mutt-send-email-mst@kernel.org>
On 2019/10/28 22:56, Michael S. Tsirkin wrote:
> On Mon, Oct 28, 2019 at 09:50:21PM +0800, gengdongjiu wrote:
>> Hi Michael,
>>
>> On 2019/10/28 16:28, Michael S. Tsirkin wrote:
>>>>> gets some testing. I'll leave this decision to the ARM maintainer. For
>>>>> ACPI parts:
>>>>>
>>>>> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
>>>> Got it, Thanks for the Reviewed-by from Michael.
>>>>
>>>> Hi Michael,
>>>> According to discussion with QEMU community, I finished and developed the whole ARM RAS virtualization solution, and introduce the ARM APEI table in the first time.
>>>> For the newly created files, which are mainly about ARM APEI/GHES part,I would like to maintain them. If you agree it, whether I can add new maintainers[1]? thanks a lot.
>>>>
>>>>
>>>> [1]:
>>>> +ARM APEI Subsystem
>>>> +M: Dongjiu Geng <gengdongjiu@huawei.com>
>>>> +M: Xiang zheng <zhengxiang9@huawei.com>
>>>> +L: qemu-arm@nongnu.org
>>>> +S: Maintained
>>>> +F: hw/acpi/acpi_ghes.c
>>>>
>>> I think for now you want to be a designated reviewer. So I'd use an R:
>>> tag.
>>
>> Thanks for the reply.
>> I want to be a maintainer for my newly created files, so whether I can use M: tag. I would like to contribute some time to maintain that, thanks a lot.
>
> This will fundamentally be up to Peter.
Thanks.
Hi Peter,
what do you think about it?
>
>
>
>>>
>>>>>
>>>>>> ---
> .
>
next prev parent reply other threads:[~2019-10-28 15:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 3:24 [PATCH v20 0/5] Add ARMv8 RAS virtualization support in QEMU Xiang Zheng
2019-10-26 3:24 ` [PATCH v20 1/5] hw/arm/virt: Introduce a RAS machine option Xiang Zheng
2019-10-26 3:24 ` [PATCH v20 2/5] docs: APEI GHES generation and CPER record description Xiang Zheng
2019-10-26 3:24 ` [PATCH v20 3/5] ACPI: Add APEI GHES table generation support Xiang Zheng
2019-10-27 10:14 ` Michael S. Tsirkin
2019-10-30 8:51 ` Xiang Zheng
2019-10-26 3:24 ` [PATCH v20 4/5] KVM: Move hwpoison page related functions into kvm-all.c Xiang Zheng
2019-10-26 3:24 ` [PATCH v20 5/5] target-arm: kvm64: handle SIGBUS signal from kernel or KVM Xiang Zheng
2019-10-27 10:17 ` [PATCH v20 0/5] Add ARMv8 RAS virtualization support in QEMU Michael S. Tsirkin
2019-10-28 3:16 ` Xiang Zheng
2019-10-28 4:01 ` gengdongjiu
2019-10-28 8:28 ` Michael S. Tsirkin
2019-10-28 12:41 ` gengdongjiu
2019-10-28 13:50 ` gengdongjiu
2019-10-28 14:56 ` Michael S. Tsirkin
2019-10-28 15:10 ` gengdongjiu [this message]
2019-10-28 15:16 ` Peter Maydell
2019-10-29 7:06 ` gengdongjiu
2019-10-28 13:11 ` Peter Maydell
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=a16f00df-98cd-3469-1c64-d9d7a6ccaccf@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=james.morse@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=lersek@redhat.com \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=shannon.zhaosl@gmail.com \
--cc=wanghaibin.wang@huawei.com \
--cc=xuwei5@huawei.com \
--cc=zhengxiang9@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 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).