From: Stephen Hemminger <stephen@networkplumber.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, pshelar@nicira.com,
cwang@twopensource.com, nicolas.dichtel@6wind.com,
ebiederm@xmission.com, david@gibson.dropbear.id.au,
sfeldma@cumulusnetworks.com, sucheta.chakraborty@qlogic.com
Subject: Re: [patch net-next v2 1/2] rtnetlink: allow to register ops without ops->setup set
Date: Wed, 25 Jun 2014 11:45:00 -0700 [thread overview]
Message-ID: <20140625114500.7c09874e@haswell> (raw)
In-Reply-To: <1403715503-9059-1-git-send-email-jiri@resnulli.us>
On Wed, 25 Jun 2014 18:58:22 +0200
Jiri Pirko <jiri@resnulli.us> wrote:
> So far, it is assumed that ops->setup is filled up. But there might be
> case that ops might make sense even without ->setup. In that case,
> forbid to newlink and dellink.
>
> This allows to register simple rtnl link ops containing only ->kind.
> That allows consistent way of passing device kind (either device-kind or
> slave-kind) to userspace.
>
> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
Can't we fix these kind of devices to all create/delete. At least
allow delete.
next prev parent reply other threads:[~2014-06-25 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 16:58 [patch net-next v2 1/2] rtnetlink: allow to register ops without ops->setup set Jiri Pirko
2014-06-25 16:58 ` [patch net-next v2 2/2] openvswitch: introduce rtnl ops stub Jiri Pirko
2014-06-25 17:16 ` [patch net-next v2 1/2] rtnetlink: allow to register ops without ops->setup set Eric W. Biederman
2014-06-25 18:45 ` Stephen Hemminger [this message]
2014-06-26 7:46 ` Jiri Pirko
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=20140625114500.7c09874e@haswell \
--to=stephen@networkplumber.org \
--cc=cwang@twopensource.com \
--cc=davem@davemloft.net \
--cc=david@gibson.dropbear.id.au \
--cc=ebiederm@xmission.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pshelar@nicira.com \
--cc=sfeldma@cumulusnetworks.com \
--cc=sucheta.chakraborty@qlogic.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).