linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: dwmw2@infradead.org
Cc: thomas@horsten.com, hch@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.21-rc1: byteorder.h breaks with __STRICT_ANSI__ defined (trivial)
Date: Tue, 06 May 2003 20:06:38 -0700 (PDT)	[thread overview]
Message-ID: <20030506.200638.78728404.davem@redhat.com> (raw)
In-Reply-To: <1052255946.7532.66.camel@imladris.demon.co.uk>

   From: David Woodhouse <dwmw2@infradead.org>
   Date: Tue, 06 May 2003 22:19:06 +0100

   The correct fix is to provide a userland-only version of cdrom.h which
   doesn't use the private kernel types.h. Or a file containing _only_
   those parts which can be shared between kernel and userland, defined
   using standard types such as uint32_t etc. 

Correct in your world only :-)

Listen, what do you think is the latency every time I add something
to rtnetlink.h or pfkeyv2.h?  Should I just sit and twiddle my thumbs
waiting for everyone to update their glibc or kernel-headers or
whatever package before they can compile networking apps using the
new feature?

The fact is, until that issue is solved, we have to assume that
programs are going to include kernel headers and there is nothing
we can do about it until we provide a better situation than exists
now.

Therefore, making inclusions of these kinds of headers work from
userspace is in some sense a requirement.

  reply	other threads:[~2003-05-07  4:01 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06  9:16 [PATCH] 2.4.21-rc1: byteorder.h breaks with __STRICT_ANSI__ defined (trivial) 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 [this message]
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
     [not found] <20030506110259.A29633@infradead.org>
2003-05-06 10:24 ` Thomas Horsten
2003-11-06 17:36 Martin Schlemmer
2003-11-06 17:37 ` David S. Miller
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

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=20030506.200638.78728404.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@horsten.com \
    /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).