lkml.org 
[lkml]   [2004]   [Nov]   [30]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateTue, 30 Nov 2004 06:31:26 +0100
FromHerbert Poetzl <>
SubjectRe: [RFC] Splitting kernel headers and deprecating __KERNEL__
On Mon, Nov 29, 2004 at 03:00:17PM -0800, Linus Torvalds wrote:
> 
> 
> 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.

except for the user land kernel helpers ;)
via call_usermodehelper()

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

sorry too,
Herbert

> -
> 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/
-
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: 2005-03-22 14:08    [from the cache]
©2003-2008