From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Xiao Guangrong" <xiaoguangrong.eric@gmail.com>,
"Ben Warren" <ben@skyportsystems.com>,
"open list:Virt" <qemu-arm@nongnu.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/3] hw/nvram/fw_cfg: Remove various typedefs from "qemu/typedefs.h"
Date: Mon, 14 Jan 2019 13:06:46 -0500 [thread overview]
Message-ID: <20190114130617-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <c7323df9-a2c0-80f9-d9ba-065279ff6126@redhat.com>
On Mon, Jan 14, 2019 at 06:52:21PM +0100, Paolo Bonzini wrote:
> On 14/01/19 16:49, Michael S. Tsirkin wrote:
> > On Mon, Jan 14, 2019 at 02:08:27PM +0100, Philippe Mathieu-Daudé wrote:
> >> There are only three include files requiring these typedefs, let them
> >> include "hw/nvram/fw_cfg.h" directly to simplify "qemu/typedefs.h".
> >>
> >> To clean "qemu/typedefs.h", move the declarations to "hw/nvram/fw_cfg.h".
> >> Reorder two function declarations to avoid forward typedef declarations.
> >>
> >> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> >> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> >> ---
> >> include/hw/acpi/vmgenid.h | 1 +
> >> include/hw/arm/virt.h | 1 +
> >> include/hw/mem/nvdimm.h | 1 +
> >> include/hw/nvram/fw_cfg.h | 22 ++++++++++++----------
> >> include/qemu/typedefs.h | 4 ----
> >> 5 files changed, 15 insertions(+), 14 deletions(-)
> >
> > I am sorry I don't understand what this patchset is about.
> > Supposed to be a cleanup but instead it pulls
> > fw cfg into any user of unrelated headers.
> >
> > More lines of code slower builds what's to like?
> >
> > Shared typedefs is what typedefs.h is about.
> > These are clearly shared so let's keep it simple.
>
> I can see why this patch can be a bit controversial. Personally I think
> it's okay either way (which generally tends to favor the status quo).
>
> Paolo
True - not something to lose sleep over.
--
MST
next prev parent reply other threads:[~2019-01-14 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 13:08 [Qemu-devel] [PATCH v2 0/3] typedefs: Remove scarcely used declarations Philippe Mathieu-Daudé
2019-01-14 13:08 ` [Qemu-devel] [PATCH v2 1/3] hw/nvram/fw_cfg: Remove various typedefs from "qemu/typedefs.h" Philippe Mathieu-Daudé
2019-01-14 14:23 ` Laszlo Ersek
2019-01-14 15:49 ` Michael S. Tsirkin
2019-01-14 17:52 ` Paolo Bonzini
2019-01-14 18:06 ` Michael S. Tsirkin [this message]
2019-01-14 13:08 ` [Qemu-devel] [PATCH v2 2/3] ui/console: Remove MouseTransformInfo from qemu/typedefs.h Philippe Mathieu-Daudé
2019-01-14 14:05 ` Gerd Hoffmann
2019-01-14 13:08 ` [Qemu-devel] [PATCH v2 3/3] ui/console: Remove PixelFormat " Philippe Mathieu-Daudé
2019-01-14 14:05 ` Gerd Hoffmann
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=20190114130617-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ben@skyportsystems.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).