From: Harvey Harrison <harvey.harrison@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
"Al Viro" <viro@ZenIV.linux.org.uk>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: [PATCH] x86: !x & y typo in mtrr code
Date: Wed, 30 Apr 2008 08:35:34 -0700 [thread overview]
Message-ID: <1209569734.24729.65.camel@brick> (raw)
In-Reply-To: <20080430123536.GD30735@elte.hu>
On Wed, 2008-04-30 at 14:35 +0200, Ingo Molnar wrote:
> We for one simply concentrate on the the things that we think makes it
> more likely to find bugs. For example we build and boot x86.git with
> many different configs before every pull request. In practice that
> catches far more tester-critical bugs than Sparse - and we know that
> simply from the fact because we use both methods and have a good
> comparison of the results. We also work on automating Sparse checks in
> the future but as i said it, it's not easy.
>
That's precisely why I've been sending all of the sparse cleanup patches
lately, to try and get the output down to something more managable. You
may want to upgrade your sparse to one that understands __cold though.
Harvey
next prev parent reply other threads:[~2008-04-30 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 4:00 [PATCH] x86: !x & y typo in mtrr code Harvey Harrison
2008-04-27 4:20 ` Al Viro
2008-04-29 21:04 ` Ingo Molnar
2008-04-30 6:46 ` Björn Steinbrink
2008-04-30 7:46 ` Thomas Gleixner
2008-04-30 9:32 ` Ingo Molnar
2008-04-30 12:17 ` Björn Steinbrink
2008-04-30 12:35 ` Ingo Molnar
2008-04-30 15:35 ` Harvey Harrison [this message]
2008-04-30 18:06 ` Ingo Molnar
2008-05-06 18:24 ` Valdis.Kletnieks
2008-04-28 11:27 ` Ingo Molnar
2008-04-28 15:10 ` Harvey Harrison
2008-04-28 23:16 ` Pallipadi, Venkatesh
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=1209569734.24729.65.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=B.Steinbrink@gmx.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
--cc=viro@ZenIV.linux.org.uk \
/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