All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: zbr@ioremap.net
Cc: nhorman@tuxdriver.com, netdev@vger.kernel.org
Subject: Re: [Patch 1/5] Network Drop Monitor: Add netlink protocol identifer
Date: Tue, 03 Mar 2009 14:17:49 -0800 (PST)	[thread overview]
Message-ID: <20090303.141749.210780391.davem@davemloft.net> (raw)
In-Reply-To: <20090303182006.GB29236@ioremap.net>

From: Evgeniy Polyakov <zbr@ioremap.net>
Date: Tue, 3 Mar 2009 21:20:06 +0300

> Why do you want to use own family instead of using existing netlink
> helpers like connector or genetlink?

Yes, indeed, use genetlink for this.

We don't add new core netlink protocols any more with it's
fixed address space of link types.

  parent reply	other threads:[~2009-03-03 22:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 17:00 [Patch 1/5] Network Drop Monitor: Add netlink protocol identifer Neil Horman
2009-03-03 18:20 ` Evgeniy Polyakov
2009-03-03 19:00   ` Neil Horman
2009-03-03 19:04     ` Evgeniy Polyakov
2009-03-03 19:41       ` Neil Horman
2009-03-03 22:17   ` David Miller [this message]
2009-03-04 15:39     ` Neil Horman
2009-03-11 19:46 ` Neil Horman

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=20090303.141749.210780391.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=zbr@ioremap.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.