Kumar Gala writes:
> So after all of this its not clear to me if its acceptable to kill
> all users of in the kernel and to move code that
> exists in to for arch's that need it.
doesn't describe any part of the user/kernel ABI, so
we should be OK to kill it. I would say we should remove
On Aug 17, 2005, at 5:07 AM, Miklos Szeredi wrote:
They are provided by _one_ kernel, not necessarily the running
kernel.
No, they're provided by packages like glibc-kernheaders or similar
that are maintained separately.
Yes. And "maintenance" I presume means "copy" the kernel headers
> > They are provided by _one_ kernel, not necessarily the running kernel.
>
> No, they're provided by packages like glibc-kernheaders or similar
> that are maintained separately.
Yes. And "maintenance" I presume means "copy" the kernel headers and
do some cleanup to be compliant to the relevant
On Wed, Aug 17, 2005 at 11:15:39AM +0200, Miklos Szeredi wrote:
> They are provided by _one_ kernel, not necessarily the running kernel.
No, they're provided by packages like glibc-kernheaders or similar
that are maintained separately. They're split from the kernel headers
and we don't need to ke
> > There are perfectly valid uses of kernel headers from userspace. For
> > example if a program uses the netlink interface, it should include
> > . It's the interface definition after all.
> >
> > Glibc headers also include and in quite few places.
>
> But these files in /usr/include/ aren'
On Wed, Aug 17, 2005 at 10:56:24AM +0200, Miklos Szeredi wrote:
> > On Wed, Aug 17, 2005 at 12:43:37AM -0500, Kumar Gala wrote:
> > > >I concur, in fact we should really kill that thing off entirely.
> > >
> > > I'm all for killing it off entirely but got some feedback that on
> > > i386 segment
> On Wed, Aug 17, 2005 at 12:43:37AM -0500, Kumar Gala wrote:
> > >I concur, in fact we should really kill that thing off entirely.
> >
> > I'm all for killing it off entirely but got some feedback that on
> > i386 segment.h can be included by userspace programs.
>
> No kernel headers can be in
On Wed, Aug 17, 2005 at 12:43:37AM -0500, Kumar Gala wrote:
> >I concur, in fact we should really kill that thing off entirely.
>
> I'm all for killing it off entirely but got some feedback that on
> i386 segment.h can be included by userspace programs.
No kernel headers can be included by user
On Wed, 17 Aug 2005, Kumar Gala wrote:
> I'm all for killing it off entirely but got some feedback that on i386
> segment.h can be included by userspace programs.
>
> Here is the in kernel consumers that are outside of arch specific directories:
> ./drivers/video/q40fb.c:#include
M68k-only, so
On Aug 16, 2005, at 10:33 PM, David S. Miller wrote:
From: Paul Mackerras <[EMAIL PROTECTED]>
Date: Wed, 17 Aug 2005 11:38:20 +1000
Kumar Gala writes:
Made a dummy include like it is in ppc64 and removed
any
users if it in arch/ppc.
Why can't we just delete asm-ppc/segment.h (and
From: Paul Mackerras <[EMAIL PROTECTED]>
Date: Wed, 17 Aug 2005 11:38:20 +1000
> Kumar Gala writes:
>
> > Made a dummy include like it is in ppc64 and removed any
> > users if it in arch/ppc.
>
> Why can't we just delete asm-ppc/segment.h (and asm-ppc64/segment.h
> too, for that matter) entirel
Kumar Gala writes:
> Made a dummy include like it is in ppc64 and removed any
> users if it in arch/ppc.
Why can't we just delete asm-ppc/segment.h (and asm-ppc64/segment.h
too, for that matter) entirely?
Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bod
Made a dummy include like it is in ppc64 and removed any
users if it in arch/ppc.
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
commit f63ab7e926d6c5e96de501ec9eac7f28af188a65
tree adcc67a572ec8e4d1520a7a5493ea909028e76f9
parent d88b795bc4c4b59c29a98e2a551c2ad4d65901c5
author Kumar K. Gala <
13 matches
Mail list logo
