From: andrzej zaborowski <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] clean build: Add bt-host.h
Date: Fri, 20 Mar 2009 15:51:52 +0100 [thread overview]
Message-ID: <fb249edb0903200751x57cd4db9g9eefa6678c304618@mail.gmail.com> (raw)
In-Reply-To: <49B77E19.3010609@siemens.com>
2009/3/11 Jan Kiszka <jan.kiszka@siemens.com>:
> andrzej zaborowski wrote:
,,,
>> Is it?
>> struct HCIInfo is defined in net.h so maybe this one belongs there too.
>>
>> I'd much rather turn off the unhelpful warnings, some of them caused
>> developers to add code that is both more hacky and slower. I also
>> think we could save many header files like the hw/virtio-*.h, at this
>> granularity they don't help with compile times which was the reason
>> vl.h was split.
>
> I think we see so far a net gain from the warnings as several real bugs
> were caught that way.
Some of the warnings are useful and some are just "if leave your house
a brick might fall on your head and you might die" type.
> And in this case the warning pointed out unclean
> header organization (internal API exports mixed up with generic
> bluetooth types). The goal should not be "as few headers as possible"
> but "one header per reasonably partitioned API".
Right, this makes browsing the headers much easier when looking up a
prototype. This change is in the opposite direction.
(and why is it less hacky?)
Cheers
next prev parent reply other threads:[~2009-03-20 14:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 19:00 [Qemu-devel] [PATCH 0/7] clean build - eliminate warnings Jan Kiszka
2009-02-21 19:00 ` [Qemu-devel] [PATCH 1/7] clean build: Add bt_host_hci prototype Jan Kiszka
2009-03-08 14:56 ` [Qemu-devel] " Jan Kiszka
2009-03-08 18:44 ` Aurelien Jarno
2009-03-08 19:56 ` [Qemu-devel] [PATCH] clean build: Add bt-host.h Jan Kiszka
2009-03-10 21:43 ` Aurelien Jarno
2009-03-10 23:03 ` andrzej zaborowski
2009-03-11 9:02 ` [Qemu-devel] " Jan Kiszka
2009-03-20 14:51 ` andrzej zaborowski [this message]
2009-02-21 19:00 ` [Qemu-devel] [PATCH 5/7] clean build: Fix remaining cris warnings Jan Kiszka
2009-02-21 23:03 ` Stuart Brady
2009-02-21 23:12 ` Stuart Brady
2009-02-21 23:13 ` Laurent Desnogues
2009-02-22 10:36 ` [Qemu-devel] [PATCH v2 " Jan Kiszka
2009-02-22 14:14 ` Edgar E. Iglesias
2009-02-21 23:14 ` [Qemu-devel] [PATCH " Paul Brook
2009-02-21 19:00 ` [Qemu-devel] [PATCH 4/7] clean build: Fix arm build warnings Jan Kiszka
2009-03-07 21:48 ` Aurelien Jarno
2009-02-21 19:00 ` [Qemu-devel] [PATCH 3/7] arm: Fix gic_irq_state.level bitfield type Jan Kiszka
2009-03-07 21:48 ` Aurelien Jarno
2009-02-21 19:00 ` [Qemu-devel] [PATCH 2/7] clean build: Fix irq_info and pic_info related warnings Jan Kiszka
2009-02-21 19:00 ` [Qemu-devel] [PATCH 6/7] clean build: Fix remaining m68k warnings Jan Kiszka
2009-03-07 21:48 ` Aurelien Jarno
2009-02-21 19:00 ` [Qemu-devel] [PATCH 7/7] clean build: Fix remaining sh4 warnings Jan Kiszka
2009-02-21 19:43 ` [Qemu-devel] [PATCH 0/7] clean build - eliminate warnings Laurent Desnogues
2009-02-21 20:09 ` [Qemu-devel] " Jan Kiszka
2009-02-21 23:08 ` Laurent Desnogues
2009-02-22 10:39 ` Jan Kiszka
2009-02-22 11:09 ` Jan Kiszka
2009-02-22 0:59 ` Edgar E. Iglesias
2009-02-22 10:20 ` Jan Kiszka
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=fb249edb0903200751x57cd4db9g9eefa6678c304618@mail.gmail.com \
--to=balrogg@gmail.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).