lkml.org 
[lkml]   [2004]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] Splitting kernel headers and deprecating __KERNEL__


On Mon, 29 Nov 2004, Alexandre Oliva wrote:
>
> I don't see it as obvious at all. The need for an agreement between
> two parties on an ABI doesn't imply that one party gets to define it
> and the other gets to follow it.

Sorry, but that's not how it works.

He who writes the code decides what it is. In this case, if the kernel
does a new extension, it's the kernel that gets to decide what it is.
Full stop.

If glibc wants to do something new, go wild. The kernel won't care.

And that's really the fundamental issue. The kernel does not care what
user land does. The kernel exports functionality, the kernel does _not_
ask user land to help.

That _does_ make it a one-way street. Sorry.

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2009-11-18 23:46    [from the cache]
©2003-2011 Jasper Spaans