| To: | Evgeniy Polyakov <johnpol@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Kernel connector - userspace <-> kernelspace "linker". |
| From: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
| Date: | Tue, 21 Sep 2004 13:22:35 +0100 |
| Cc: | netdev@xxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <20040921124623.GA6942@uganda.factory.vocord.ru> |
| References: | <1095331899.18219.58.camel@uganda> <20040921124623.GA6942@uganda.factory.vocord.ru> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
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". |
| Previous by Date: | Re: Kernel connector - userspace <-> kernelspace "linker"., Richard B. Johnson |
|---|---|
| Next by Date: | Re: [PATCH + RFC] neighbour/ARP cache scalability, Harald Welte |
| Previous by Thread: | Re: Kernel connector - userspace <-> kernelspace "linker"., Evgeniy Polyakov |
| Next by Thread: | Re: Kernel connector - userspace <-> kernelspace "linker"., Evgeniy Polyakov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |