mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"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: Tue, 06 May 2008 14:24:17 -0400	[thread overview]
Message-ID: <4368.1210098257@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 30 Apr 2008 08:35:34 PDT." <1209569734.24729.65.camel@brick>

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

On Wed, 30 Apr 2008 08:35:34 PDT, Harvey Harrison said:
> 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.

What release of sparse would that be?  Fedora ships one tagged as 0.4.1-2.fc9,
but that says:

include/linux/kernel.h:135:52: error: attribute '__cold__': unknown attribute

But you go look at Documentation/sparse.txt and it points you to:

"You can get latest released versions from the Sparse homepage at
http://www.kernel.org/pub/linux/kernel/people/josh/sparse/ "

which says 0.4.1 is the latest released version.  So is this a git-only feature?

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2008-05-06 18:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27  4:00 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
2008-04-30 18:06               ` Ingo Molnar
2008-05-06 18:24               ` Valdis.Kletnieks [this message]
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=4368.1210098257@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=B.Steinbrink@gmx.de \
    --cc=harvey.harrison@gmail.com \
    --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

all inboxes | Powered by JetHome®