public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <kpfleming@cox.net>
To: "ismail (cartman) donmez" <kde@myrealbox.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] include/linux/sysctl.h needs linux/compiler.h
Date: Sat, 31 May 2003 16:37:42 -0700	[thread overview]
Message-ID: <3ED93CC6.30200@cox.net> (raw)
In-Reply-To: <200306010016.05548.kde@myrealbox.com>

ismail (cartman) donmez wrote:
> On Sunday 01 June 2003 00:08, Kevin P. Fleming wrote:
> 
> 
>>Right. But until such time as that happens (even if started today that's
>>many months away), real world libraries need to be compiled to be used
>>against the new kernel.
>>
> 
> Yes I reported to binutils hackers that this change broke binutils ( + glibc ) 
> but kernel guys just say "do not include kernel headers in userspace" . 
> 

Oh, I saw that discussion. I fully agree. If I can help the process of 
creating a sanitized userspace set of kernel headers I'll be happy to.

In the meantime, a small change to a kernel header, that provides _zero_ 
functional difference to the kernel itself (it's only there for source 
code checkers, as best I can tell) shouldn't break existing userspace 
libraries.

If it's going to, then we should just go ahead and break everything and 
get it done right. It's late in the 2.6 game, but the first few steps on 
the path have already been taken.


  reply	other threads:[~2003-05-31 23:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31 16:18 [PATCH] include/linux/sysctl.h needs linux/compiler.h Kevin P. Fleming
2003-05-31 19:32 ` Christoph Hellwig
2003-05-31 19:56   ` Kevin P. Fleming
2003-05-31 20:25 ` ismail (cartman) donmez
2003-05-31 20:32   ` Kevin P. Fleming
2003-05-31 20:58     ` ismail (cartman) donmez
2003-05-31 21:08       ` Kevin P. Fleming
2003-05-31 21:16         ` ismail (cartman) donmez
2003-05-31 23:37           ` Kevin P. Fleming [this message]
2003-06-01  8:36             ` ismail (cartman) donmez
2003-06-02  5:43               ` Martin Schlemmer
2003-06-02  7:24                 ` ismail (cartman) donmez

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=3ED93CC6.30200@cox.net \
    --to=kpfleming@cox.net \
    --cc=kde@myrealbox.com \
    --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