From: Andrew Morton <akpm@osdl.org>
To: James Morris <jmorris@redhat.com>
Cc: johnpol@2ka.mipt.ru, herbert@gondor.apana.org.au,
netdev@oss.sgi.com, davem@davemloft.net
Subject: Re: Fw: 2.6.12-rc4-mm[12] - ULOG problem
Date: Thu, 19 May 2005 09:53:34 -0700 [thread overview]
Message-ID: <20050519095334.018dd674.akpm@osdl.org> (raw)
In-Reply-To: <Xine.LNX.4.44.0505190918430.15522-100000@thoron.boston.redhat.com>
James Morris <jmorris@redhat.com> wrote:
>
> On Thu, 19 May 2005, Andrew Morton wrote:
>
> > We should remove the feature. If there is demonstrated need for multiple
> > instances then it should be done by more conventional means - syscall,
> > allocation of a device major then use the minor as a selector or whatever.
>
> I'd suggest removing the connector code completely.
>
How come? It seems sensible to have library code which consoldates the
common netlink setup and teardown stuff and which offers a higher-level
messaging API, although connector may be a bit overdesigned for that. The
fork connector guys seemed to find it useful?
next prev parent reply other threads:[~2005-05-19 16:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 3:24 Fw: 2.6.12-rc4-mm[12] - ULOG problem Andrew Morton
2005-05-19 4:49 ` Herbert Xu
2005-05-19 5:27 ` Andrew Morton
2005-05-19 6:31 ` Evgeniy Polyakov
2005-05-19 6:45 ` Andrew Morton
2005-05-19 7:06 ` Evgeniy Polyakov
2005-05-19 7:08 ` Andrew Morton
2005-05-19 7:27 ` Evgeniy Polyakov
2005-05-19 13:19 ` James Morris
2005-05-19 16:53 ` Andrew Morton [this message]
2005-05-19 17:09 ` James Morris
2005-05-19 18:54 ` David S. Miller
2005-05-19 18:48 ` David S. Miller
2005-05-20 6:27 ` Evgeniy Polyakov
2005-05-19 18:42 ` David S. Miller
2005-05-20 6:27 ` Evgeniy Polyakov
2005-05-19 18:44 ` David S. Miller
2005-05-20 6:39 ` Evgeniy Polyakov
2005-05-20 11:42 ` jamal
2005-05-20 14:15 ` Evgeniy Polyakov
2005-05-19 13:16 ` Fw: " James Morris
2005-05-19 13:46 ` jamal
2005-05-19 18:49 ` David S. Miller
2005-05-20 6:25 ` Evgeniy Polyakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050519095334.018dd674.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@redhat.com \
--cc=johnpol@2ka.mipt.ru \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).