linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Helge Deller <deller@gmx.de>,
	David Miller <davem@davemloft.net>,
	jaswinder@kernel.org, mingo@elte.hu, x86@kernel.org,
	linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
	Kyle McMartin <kyle@mcmartin.ca>
Subject: Re: Confusion in usr/include/asm-generic/fcntl.h
Date: Wed, 21 Jan 2009 09:57:28 -0800	[thread overview]
Message-ID: <49776208.8050704@kernel.org> (raw)
In-Reply-To: <20090121172837.GA4386@uranus.ravnborg.org>

Sam Ravnborg wrote:
> 
> It gives the warning only if you add -Wundef which IIRC is not default
> with -Wall. And using the "__BITS_PER_LONG == 64" the risk of gitting
> the expression wrong is much higher than the simpler variant where
> you only write:
> 
>     __64BIT
> 
> But I have no strong feelings for it.
> 

It's not the default, but it would be nice if we could start using it.

	-hpa

  reply	other threads:[~2009-01-21 17:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1232496257.3123.19.camel@localhost.localdomain>
     [not found] ` <20090120.161626.93641145.davem@davemloft.net>
2009-01-21  0:24   ` Confusion in usr/include/asm-generic/fcntl.h Arnd Bergmann
2009-01-21  0:32     ` David Miller
2009-01-21  8:13       ` Helge Deller
2009-01-21  8:24         ` Arnd Bergmann
2009-01-21 11:38           ` Sam Ravnborg
2009-01-21 12:13             ` Arnd Bergmann
2009-01-21 14:29               ` Kyle McMartin
2009-01-21 16:44               ` H. Peter Anvin
2009-01-21 17:28               ` Sam Ravnborg
2009-01-21 17:57                 ` H. Peter Anvin [this message]
2009-01-27 22:35           ` Helge Deller
2009-01-21 22:25     ` Grant Grundler
2009-01-21 22:43       ` John David Anglin
2009-01-22  0:46         ` H. Peter Anvin
2009-01-22  2:52           ` John David Anglin
2009-01-22  2:56             ` H. Peter Anvin

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=49776208.8050704@kernel.org \
    --to=hpa@kernel.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=deller@gmx.de \
    --cc=jaswinder@kernel.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=x86@kernel.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).