| To: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Kernel connector - userspace <-> kernelspace "linker". |
| From: | Evgeniy Polyakov <johnpol@xxxxxxxxxxx> |
| Date: | Tue, 21 Sep 2004 18:28:53 +0400 |
| Cc: | netdev@xxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <1095769354.30743.64.camel@xxxxxxxxxxxxxxxxxxxxx> |
| Organization: | MIPT |
| References: | <1095331899.18219.58.camel@uganda> <20040921124623.GA6942@xxxxxxxxxxxxxxxxxxxxxxxx> <1095769354.30743.64.camel@xxxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | johnpol@xxxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Tue, 21 Sep 2004 13:22:35 +0100
Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
> On Maw, 2004-09-21 at 13:46, Evgeniy Polyakov wrote:
> > Connector driver adds possibility to connect various agents using
> > netlink based network.
> > One must register callback and identificator. When driver receives
> > special netlink message with appropriate identificator, appropriate
> > callback will be called.
>
> Looks sane enough to me - and it seems to fit the mentality d-bus and
> HAL want to have.
>
> Alan
>
> ps: only trivial item (and really trivial) is that the printk messages
> should be "waiting for %s".
:) Sure. If it will be in the kernel, it will not contain errors.
Evgeniy Polyakov
Only failure makes us experts. -- Theo de Raadt
|
| Previous by Date: | Re: [PATCH + RFC] neighbour/ARP cache scalability, Pekka Savola |
|---|---|
| Next by Date: | Re: Kernel connector - userspace <-> kernelspace "linker"., Buddy Lucas |
| Previous by Thread: | Re: Kernel connector - userspace <-> kernelspace "linker"., Alan Cox |
| Next by Thread: | Re: Kernel connector - userspace <-> kernelspace "linker"., Buddy Lucas |
| Indexes: | [Date] [Thread] [Top] [All Lists] |