public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH, TRIVIAL] Fix argument of BLKGETSIZE64
Date: Wed, 12 Jun 2002 15:22:48 +0200	[thread overview]
Message-ID: <jey9dkhbrr.fsf@sykes.suse.de> (raw)
In-Reply-To: <15622.54728.469214.307901@wombat.chubb.wattle.id.au> <E17I0sl-0004y0-00@wagner.rustcorp.com.au> <15623.11051.890868.154587@wombat.chubb.wattle.id.au>

Peter Chubb <peter@chubb.wattle.id.au> writes:

|> You could argue that this is a glibc bug.  But the way that glibc
|> generates the include/linux headers is just to copy them from some
|> kernel tree or other, with a little mangling on the side.

Glibc does not do anything with the kernel headers besides using some of
them.  Especially it does not generate any of them.  The fact that the
distributions usually pack the kernel headers together with the glibc
headers does not mean that the kernel headers belong to glibc.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2002-06-12 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12  5:02 [PATCH, TRIVIAL] Fix argument of BLKGETSIZE64 Peter Chubb
2002-06-12  5:41 ` Rusty Russell
2002-06-12 11:06   ` Peter Chubb
2002-06-12 13:22     ` Andreas Schwab [this message]
2002-06-12 13:47     ` David Woodhouse
2002-06-12 20:19       ` Peter Chubb
2002-06-12 20:45         ` David Woodhouse

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=jey9dkhbrr.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@chubb.wattle.id.au \
    --cc=rusty@rustcorp.com.au \
    /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