From: "David S. Miller" <davem@redhat.com>
To: azarah@gentoo.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.21-rc1: byteorder.h breaks with __STRICT_ANSI__ defined (trivial)
Date: Thu, 6 Nov 2003 09:37:46 -0800 [thread overview]
Message-ID: <20031106093746.5cc8066e.davem@redhat.com> (raw)
In-Reply-To: <1068140199.12287.246.camel@nosferatu.lan>
On Thu, 06 Nov 2003 19:36:39 +0200
Martin Schlemmer <azarah@gentoo.org> wrote:
> On Tue, 2003-05-06 at 04:19, David S. Miller wrote:
> > On Tue, 2003-05-06 at 02:16, Thomas Horsten wrote:
> > > The following patch fixes the problem:
> >
> > Making the u64 swabbing functions unavailable is not an
> > acceptable solution.
> >
>
> Sorry to dig this up again, but wont __STRICT_ANSI__ assume
> that the program will not use u64 functions (as the program/compiler
> is supposed to adhere to ansi standards)?
It may make indirect use of inline functions in the kernel headers
in question, which themselves need to use the u64 type.
next prev parent reply other threads:[~2003-11-06 17:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 17:36 [PATCH] 2.4.21-rc1: byteorder.h breaks with __STRICT_ANSI__ defined (trivial) Martin Schlemmer
2003-11-06 17:37 ` David S. Miller [this message]
2003-11-06 18:32 ` Martin Schlemmer
2003-11-06 18:42 ` Martin Schlemmer
2003-11-06 19:37 ` David S. Miller
2003-11-06 20:09 ` Martin Schlemmer
2003-11-06 20:05 ` David S. Miller
2003-11-06 20:29 ` Martin Schlemmer
2003-11-06 20:27 ` David S. Miller
2003-11-06 21:18 ` Martin Schlemmer
2003-11-06 21:18 ` David S. Miller
2003-11-06 21:59 ` Martin Schlemmer
2003-11-06 21:24 ` Daniel Jacobowitz
2003-11-06 20:40 ` H. Peter Anvin
2003-11-06 22:31 ` David S. Miller
2003-11-06 23:40 ` H. Peter Anvin
2003-11-06 21:21 ` Daniel Jacobowitz
[not found] ` <1068489427.7910.147.camel@nosferatu.lan>
[not found] ` <3FAFE1E2.2020000@zytor.com>
[not found] ` <1068589739.19849.2.camel@nosferatu.lan>
[not found] ` <20031111145805.45206335.davem@redhat.com>
2003-11-15 13:09 ` [PATCH 2.4] " Martin Schlemmer
2003-11-15 13:24 ` [PATCH 2.6] " Martin Schlemmer
[not found] <20030506110259.A29633@infradead.org>
2003-05-06 10:24 ` [PATCH] 2.4.21-rc1: " Thomas Horsten
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 9:16 Thomas Horsten
2003-05-06 9:19 ` David S. Miller
2003-05-06 9:38 ` Christoph Hellwig
2003-05-06 9:47 ` Thomas Horsten
2003-05-06 9:49 ` Christoph Hellwig
2003-05-06 10:03 ` David S. Miller
2003-05-06 14:10 ` Thomas Horsten
2003-05-06 13:06 ` David S. Miller
2003-05-06 15:40 ` Thomas Horsten
2003-05-07 5:50 ` ismail (cartman) donmez
2003-05-07 6:44 ` Thomas Horsten
2003-05-07 6:45 ` Christoph Hellwig
2003-05-07 5:44 ` David S. Miller
2003-05-07 6:55 ` Christoph Hellwig
2003-05-07 6:59 ` Thomas Horsten
2003-05-07 5:53 ` David S. Miller
2003-05-06 21:19 ` David Woodhouse
2003-05-07 3:06 ` David S. Miller
2003-05-07 5:26 ` Christoph Hellwig
2003-05-07 5:07 ` David S. Miller
2003-05-07 6:20 ` Christoph Hellwig
2003-05-07 5:19 ` David S. Miller
2003-05-07 6:28 ` Christoph Hellwig
2003-05-07 5:27 ` David S. Miller
2003-05-07 6:41 ` Christoph Hellwig
2003-05-07 5:42 ` David S. Miller
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=20031106093746.5cc8066e.davem@redhat.com \
--to=davem@redhat.com \
--cc=azarah@gentoo.org \
--cc=linux-kernel@vger.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).