From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Nick Piggin <npiggin@suse.de>
Cc: Valdis.Kletnieks@vt.edu,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: mmotm 2009-04-24-18-14 uploaded - NVidia indigestion
Date: Thu, 30 Apr 2009 14:03:14 +0300 [thread overview]
Message-ID: <1241089394.19252.6.camel@penberg-laptop> (raw)
In-Reply-To: <20090430103654.GB6900@wotan.suse.de>
On Thu, 2009-04-30 at 12:36 +0200, Nick Piggin wrote:
> On Tue, Apr 28, 2009 at 12:01:21PM -0400, Valdis.Kletnieks@vt.edu wrote:
> > On Tue, 28 Apr 2009 08:15:57 +0200, Nick Piggin said:
> >
> > Here's the code (pretty much *all* the code):
> >
> > > #include <linux/version.h>
> > > #include <linux/utsname.h>
> > > int main() {
> > > if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)) {
> > > return 0;
> > > } else {
> > > return 1;
> > > }
> > > }
> >
> > > Hmm, yes if you build without -O, then it appears like the compiler
> > > trips over this. I wouldn't be unhappy with just removing the BUILD_BUG_ON,
> > > but shouldn't the module be using -O[s2]?
> >
> > It's a little autoconfig chunk from vendor code that determines if we're
> > building on a sane/recent kernel. Not the sort of thing you'd expect to
> > need to invoke the frikking optimizer for program *correctness* :)
> >
> >
>
> Pekka, can you apply this please?
Applied, thanks!
next prev parent reply other threads:[~2009-04-30 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200904250133.n3P1XBJn006790@imap1.linux-foundation.org>
2009-04-25 3:06 ` Valdis.Kletnieks
2009-04-25 5:24 ` Nick Piggin
2009-04-27 18:45 ` Valdis.Kletnieks
2009-04-28 6:15 ` Nick Piggin
2009-04-28 16:01 ` Valdis.Kletnieks
2009-04-29 7:03 ` Nick Piggin
2009-04-30 10:36 ` Nick Piggin
2009-04-30 11:03 ` Pekka Enberg [this message]
2009-04-25 3:52 ` mmotm 2009-04-24-18-14 uploaded - pulseaudio causes BUG Valdis.Kletnieks
2009-04-25 4:41 ` Andrew Morton
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=1241089394.19252.6.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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®