From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
"Kashyap Chamarthy" <kchamart@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [RFC PATCH] MAINTAINERS: Cover the firmware JSON schema
Date: Fri, 3 Jul 2020 18:06:59 +0100 [thread overview]
Message-ID: <20200703170659.GQ2213227@redhat.com> (raw)
In-Reply-To: <d3b8e3f2-c565-a38e-8af6-87fd579e9045@redhat.com>
On Fri, Jul 03, 2020 at 06:58:45PM +0200, Laszlo Ersek wrote:
> On 07/03/20 18:18, Daniel P. Berrangé wrote:
> > On Fri, Jul 03, 2020 at 06:14:53PM +0200, Philippe Mathieu-Daudé wrote:
> >> Add an entry to cover firmware.json (see commit 3a0adfc9bf:
> >> schema that describes the different uses and properties of
> >> virtual machine firmware).
> >> Cc the libvirt maintainers if it ever changes.
> >>
> >> Cc: Laszlo Ersek <lersek@redhat.com>
> >> Cc: Daniel P. Berrange <berrange@redhat.com>
> >> Cc: Gerd Hoffmann <kraxel@redhat.com>
> >> Cc: Kashyap Chamarthy <kchamart@redhat.com>
> >> Cc: Michael S. Tsirkin <mst@redhat.com>
> >> Suggested-by: Laszlo Ersek <lersek@redhat.com>
> >> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> >> ---
> >> Based on a comment from Laszlo:
> >> https://www.mail-archive.com/qemu-devel@nongnu.org/msg604925.html
> >>
> >> I don't think Laszlo should be the sole maintainer, not sure
> >> who else should be listed. Gerd and Kashyap? :)
> >> Can we add it 'maintained' without specific maintainer?
> >> ---
> >> MAINTAINERS | 6 ++++++
> >> 1 file changed, 6 insertions(+)
> >>
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index dec252f38b..57c90201df 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -2601,6 +2601,12 @@ F: include/hw/i2c/smbus_master.h
> >> F: include/hw/i2c/smbus_slave.h
> >> F: include/hw/i2c/smbus_eeprom.h
> >>
> >> +Firmware schema specifications
> >> +M: Laszlo Ersek <lersek@redhat.com>
> >> +R: libvir-list@redhat.com
> >
> > FWIW, I don't think libvirt needs to review this. Our firmware handling
> > code doesn't really care what specific files exist - it just follows the
> > declared logic to pick amongst whatever exists.
>
> I request that
>
> - Phil be listed please as another maintainer (so there are two people
> that can send pull requests, if a 3rd person needs to patch this file
> for whatever reason),
>
> - Dan be listed please *at least* as an "R" person; the business logic
> written up under the @Firmware element, and lots of the initial review
> comments (in particular the suggestion to mention specific QEMU command
> line switches in the schema), had come from him.
>
> If Dan is willing to be an "M", then we can collapse both of my above
> requests into one, and Phil wouldn't have to be listed (Dan could both
> review suggested changes and submit pull requests). However, I'm raising
> this only as a technical possibility; what really matters to me is that
> Dan be CC'd on suggested changes, and that someone other than me can
> submit PRs if necessary.
I'm fine with "R", but don't want to be "M" as I don't want to be
responsible for queueing patches, etc on more parts of QEMU.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-07-03 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 16:14 [RFC PATCH] MAINTAINERS: Cover the firmware JSON schema Philippe Mathieu-Daudé
2020-07-03 16:18 ` Daniel P. Berrangé
2020-07-03 16:58 ` Laszlo Ersek
2020-07-03 17:06 ` Daniel P. Berrangé [this message]
2020-07-03 18:30 ` Philippe Mathieu-Daudé
2020-07-03 16:29 ` Kashyap Chamarthy
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=20200703170659.GQ2213227@redhat.com \
--to=berrange@redhat.com \
--cc=kchamart@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).