> > Just a random comment, but the feature freeze was October 31st. Is this
> > a repost of something we saw before then?
>
> Seems to me that it is.
That's why I asked. :)
> Besides, as patches go, this is *hardly* obtrusive
> and requires minimal changes to the kernel API. It's not like he's asking
> to integrate the whole streams driver into the kernel. I don't think the
> addition of this code will cause any new bugs to appear [the actual streams
> driver aside], do you?
The curse of 3 am posting, I thought the patch was about something else
(generic syscall registration for third party modules as mentioned months ago
on the list) in the 5 seconds I glanced at it. Having now actually read the
thing with both eyes focused, it's just sticking bodies on two already
reserved syscalls, which is pretty low impact, yeah. :)
(Although this mechanism could be USED for generic syscall registration by
third parties that don't intend to use streams, only want two syscalls, and
don't care deeply about their arguments. But it's exported GPL so that would
only ever be likely to be used for debugging purposes...)
To answer the original question for Dave: Alan Cox has now seen it, so life is
probably good for you.
> Cheers,
> Nicholas
>
>
> -
> 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/
-- http://penguicon.sf.net - Terry Pratchett, Eric Raymond, Pete Abrams, Illiad, CmdrTaco, liquid nitrogen ice cream, and caffienated jello. Well why not? - 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/