From: John Snow <jsnow@redhat.com>
To: "Zhang, Chen" <chen.zhang@intel.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Laurent Vivier <laurent@vivier.eu>,
qemu-dev <qemu-devel@nongnu.org>, Fam Zheng <fam@euphon.net>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Add unmaintained bitmap file to related field
Date: Wed, 3 Apr 2019 14:53:19 -0400 [thread overview]
Message-ID: <f6450855-94fb-c18d-448c-e3ca658087c2@redhat.com> (raw)
In-Reply-To: <9CFF81C0F6B98A43A459C9EDAD400D78060B54DD@shsmsx102.ccr.corp.intel.com>
On 4/2/19 9:25 PM, Zhang, Chen wrote:
>
>> -----Original Message-----
>> From: John Snow [mailto:jsnow@redhat.com]
>> Sent: Wednesday, April 3, 2019 5:07 AM
>> To: Zhang, Chen <chen.zhang@intel.com>; Laurent Vivier <laurent@vivier.eu>;
>> qemu-dev <qemu-devel@nongnu.org>; Fam Zheng <fam@euphon.net>
>> Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Add unmaintained bitmap
>> file to related field
>>
>>
>>
>> On 3/29/19 4:20 PM, Zhang Chen wrote:
>>> From: Zhang Chen <chen.zhang@intel.com>
>>>
>>> Add bitmap.h and bitops.h to Dirty Bitmaps field.
>>>
>>> Signed-off-by: Zhang Chen <chen.zhang@intel.com>
>>> ---
>>> MAINTAINERS | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS index 56139ac8ab..360af3e8ca
>>> 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -1773,6 +1773,8 @@ S: Supported
>>> F: util/hbitmap.c
>>> F: block/dirty-bitmap.c
>>> F: include/qemu/hbitmap.h
>>> +F: include/qemu/bitmap.h
>>> +F: include/qemu/bitops.h
>>> F: include/block/dirty-bitmap.h
>>> F: tests/test-hbitmap.c
>>> F: docs/interop/bitmaps.rst
>>>
>>
>> Actually, these bitmaps aren't the same kind as is used by the block storage
>> module -- these are a more generic, primitive kind that I have no association
>> with.
>
> OK, but these two files are lack of maintenance.
> Which maintenance area do you think these two files should belong to?
>
>
> Thanks
> Zhang Chen
>
>
Ehm, I'm not sure. Looks like Paolo and Stefan are the active developers
who have touched it the most.
Do the two of you want me to fold this into the bitmaps section so that
it has a point of contact?
--js
prev parent reply other threads:[~2019-04-03 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190329202003.30988-1-chen.zhang@intel.com>
2019-04-02 21:07 ` [Qemu-devel] [PATCH] MAINTAINERS: Add unmaintained bitmap file to related field John Snow
2019-04-03 1:25 ` Zhang, Chen
2019-04-03 18:53 ` John Snow [this message]
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=f6450855-94fb-c18d-448c-e3ca658087c2@redhat.com \
--to=jsnow@redhat.com \
--cc=chen.zhang@intel.com \
--cc=fam@euphon.net \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).