From: David Hildenbrand <david@redhat.com>
To: Xiao Guangrong <xiaoguangrong.eric@gmail.com>
Cc: Julia Suvorova <jusual@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] hw/mem/nvdimm: fix error message for 'unarmed' flag
Date: Wed, 15 Jun 2022 13:49:25 +0200 [thread overview]
Message-ID: <5e00555e-1301-b1ce-db3f-e993e6a16567@redhat.com> (raw)
In-Reply-To: <CALg51MOVVm2P5WUjnFF_xvsAk9+QYtWXjOqdU9wdCQJnv6oagg@mail.gmail.com>
On 15.06.22 13:17, Xiao Guangrong wrote:
> On Wed, Jun 15, 2022 at 4:24 PM David Hildenbrand <david@redhat.com> wrote:
>
>>>> Is that a temporary or a permanent thing? Do we know?
>>>
>>> No idea. But his last signed-off was three years ago.
>>
>> I sent a patch to Xiao, asking if he's still active in QEMU. If I don't
s/patch/mail/ :)
>> get a reply this week, I'll move forward with proposing an update to
>> MAINTAINERS as described.
>>
>
> Okay, please do it.
>
> Sorry, I am just roughly reading the mailing list of qemu & kvm usually,
> and do not get enough time to actively review or contribute on these
> fields. :-(
Not an issue, thanks for that information and thanks for your work in
the past on that!
Should I keep you entered as a reviewer for the new section?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-06-15 11:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 14:51 [PATCH] hw/mem/nvdimm: fix error message for 'unarmed' flag Julia Suvorova
2022-05-31 15:32 ` Stefan Hajnoczi
2022-06-13 15:01 ` Julia Suvorova
2022-06-13 15:09 ` Stefan Hajnoczi
2022-06-14 8:54 ` Igor Mammedov
2022-06-14 9:50 ` David Hildenbrand
2022-06-14 12:13 ` Julia Suvorova
2022-06-15 8:24 ` David Hildenbrand
2022-06-15 11:17 ` Xiao Guangrong
2022-06-15 11:49 ` David Hildenbrand [this message]
2022-06-17 12:03 ` Xiao Guangrong
2022-06-14 14:08 ` Igor Mammedov
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=5e00555e-1301-b1ce-db3f-e993e6a16567@redhat.com \
--to=david@redhat.com \
--cc=imammedo@redhat.com \
--cc=jusual@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xiaoguangrong.eric@gmail.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).