From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] Add spare checker support to the build system
Date: Tue, 07 Oct 2008 14:16:53 -0500 [thread overview]
Message-ID: <48EBB5A5.5050803@codemonkey.ws> (raw)
In-Reply-To: <48EB2FDF.8030603@redhat.com>
Gerd Hoffmann wrote:
> Hi,
>
> This adds support for running the sparse checker during the build
> process. Left it off by default for now, build becomes very noisy with
> sparse checking turned on as it has to complain alot (partly even in the
> system headers!). The qemu code base needs quite some cleanups before
> we should consider turning it on by default.
>
Applied. Thanks.
You're missing a help description for --enable-sparse. Could you please
send a new patch adding that?
Regards,
Anthony Liguori
> please apply,
> Gerd
>
next prev parent reply other threads:[~2008-10-07 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 9:46 [Qemu-devel] [patch] Add spare checker support to the build system Gerd Hoffmann
2008-10-07 19:16 ` Anthony Liguori [this message]
2008-10-07 19:21 ` Blue Swirl
2008-10-07 20:02 ` Anthony Liguori
2008-10-07 20:57 ` Gerd Hoffmann
2008-10-07 20:56 ` 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=48EBB5A5.5050803@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).