From: Adam Heath <doogie@brainfood.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Kazuo Moriwaka <moriwaka@valinux.co.jp>,
xen-devel@lists.xensource.com,
Akio Takebe <takebe_akio@jp.fujitsu.com>,
magnus.damm@gmail.com, Isaku Yamahata <yamahata@valinux.co.jp>,
Magnus Damm <magnus@valinux.co.jp>, Horms <horms@verge.net.au>
Subject: Re: Re: [PATCH 01/04] Kexec / Kdump: Generic code
Date: Wed, 18 Oct 2006 10:49:08 -0500 [thread overview]
Message-ID: <45364CF4.3030309@brainfood.com> (raw)
In-Reply-To: <C15B92BD.2B41%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> On 18/10/06 1:56 am, "Horms" <horms@verge.net.au> wrote:
>
>>> I'll check this in, so please just get rid of the if(xchg()) hacky
>>> workaround.
>> I have to say that I entirely disagree with your solution.
>> I think the solution is to get rid of -Werror. But I will
>> remove the if(xchg()) foo as you request.
>
> Holy crap! Getting rid of Werror makes Wall much less useful. We're too lazy
> to scan build output for warnings if they don't break the build.
I wrote a script that I used when I was working on kaffe. It would scan
the build output, and sort warnings based on the -W option that produces
them. It'd then give output sorted by warning option, and file. Made
it much easier to work with.
I should put that up someplace.
Was really handy when a warning was in some .h file, so would be shown
several thousand times in the build log, but was really only one problem.
next prev parent reply other threads:[~2006-10-18 15:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 8:33 [PATCH 00/04] Kexec / Kdump: Release 20061016 (xen-unstable-11760) Magnus Damm
2006-10-16 8:33 ` [PATCH 01/04] Kexec / Kdump: Generic code Magnus Damm
2006-10-16 14:03 ` Keir Fraser
2006-10-17 1:25 ` Horms
2006-10-17 6:56 ` Keir Fraser
2006-10-18 1:00 ` Horms
2006-10-18 7:15 ` Keir Fraser
2006-10-18 8:13 ` Horms
2006-10-17 6:36 ` Magnus Damm
2006-10-17 14:49 ` Keir Fraser
2006-10-17 15:05 ` Mark Williamson
2006-10-17 20:54 ` Keir Fraser
2006-10-17 22:38 ` Mark Williamson
2006-10-18 7:08 ` Keir Fraser
2006-10-18 0:56 ` Horms
2006-10-18 7:13 ` Keir Fraser
2006-10-18 8:09 ` Horms
2006-10-18 15:49 ` Adam Heath [this message]
2006-10-16 8:33 ` [PATCH 02/04] Kexec / Kdump: Code shared between x86_32 and x86_64 Magnus Damm
2006-10-16 8:33 ` [PATCH 03/04] Kexec / Kdump: x86_32 specific code Magnus Damm
2006-10-16 8:33 ` [PATCH 04/04] Kexec / Kdump: x86_64 " Magnus Damm
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=45364CF4.3030309@brainfood.com \
--to=doogie@brainfood.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=horms@verge.net.au \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=magnus.damm@gmail.com \
--cc=magnus@valinux.co.jp \
--cc=moriwaka@valinux.co.jp \
--cc=takebe_akio@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.