Messages in this thread | | | Date | Tue, 30 Sep 2003 14:42:38 +0200 | From | Jens Axboe <> | Subject | Re: Kernel includefile bug not fixed after a year :-( |
| |
On Tue, Sep 30 2003, David S. Miller wrote: > On Tue, 30 Sep 2003 14:28:32 +0200 > Jens Axboe <axboe@suse.de> wrote: > > > On Tue, Sep 30 2003, David S. Miller wrote: > > > On Tue, 30 Sep 2003 14:12:06 +0200 > > > Andreas Steinmetz <ast@domdv.de> wrote: > > > > > > Indeed, and equally someone tell me where all the IPSEC socket > > > interface defines are in glibc? It doesn't matter which tree > > > you check it won't be there. > > > > Did you notify them of the addition? > > Nope, and I don't expect them to be checking all the time. > > This is as much kernel people's problem as glibc people's. > We, as kernel people, need a system that the glibc people can > get this crap automatically. The glibc folks can then just use > it and everything just works.
Yep, the 'notify them' implies active effort from the kernel developers.
> > Well then change that to 'if you include kernel headers from your user > > apps, be prepared to pick fix the breakage'. > > There is a very small amount of effort necessary to fix this > particular problem, it won't be the end of the world if we fix the > kernel header in the actual kernel sources for them.
I'm sure Joerg is quite capable of fixing the problem and making a patch. That is the least he can do if he wants the problem to be fixed, whining is well known to be a lot less effective than that.
-- Jens Axboe
- 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/
| |