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 <ler...@redhat.com> > Cc: Daniel P. Berrange <berra...@redhat.com> > Cc: Gerd Hoffmann <kra...@redhat.com> > Cc: Kashyap Chamarthy <kcham...@redhat.com> > Cc: Michael S. Tsirkin <m...@redhat.com> > Suggested-by: Laszlo Ersek <ler...@redhat.com> > Signed-off-by: Philippe Mathieu-Daudé <phi...@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 <ler...@redhat.com> > +R: libvir-l...@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. 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 :|
