From: David Miller <davem@davemloft.net>
To: ogerlitz@mellanox.com
Cc: roland@kernel.org, netdev@vger.kernel.org, erezsh@mellanox.co.il
Subject: Re: [PATCH net-next V4] IB/ipoib: Add rtnl_link_ops support
Date: Thu, 20 Sep 2012 16:58:12 -0400 (EDT) [thread overview]
Message-ID: <20120920.165812.1484686663057692048.davem@davemloft.net> (raw)
In-Reply-To: <1347551797-2495-2-git-send-email-ogerlitz@mellanox.com>
From: Or Gerlitz <ogerlitz@mellanox.com>
Date: Thu, 13 Sep 2012 18:56:36 +0300
> Add rtnl_link_ops to IPoIB, with the first usage being child device
> create/delete through them. Childs devices are now either legacy ones,
> created/deleted through the ipoib sysfs entries, or RTNL ones.
>
> Adding support for RTNL childs involved refactoring of ipoib_vlan_add
> which is now used by both the sysfs and the link_ops code.
>
> Also, added ndo_uninit entry to support calling unregister_netdevice_queue
> from the rtnl dellink entry. This required removal of calls to
> ipoib_dev_cleanup from the driver in flows which use unregister_netdevice,
> since the networking core will invoke ipoib_uninit which does exactly that.
>
> Signed-off-by: Erez Shitrit <erezsh@mellanox.co.il>
> Signed-off-by: Or Gerlitz <ogerlitz@mellanox.com>
Applied to net-next, thanks.
next prev parent reply other threads:[~2012-09-20 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 15:56 [PATCH net-next V4 0/2] Add rtnl_link_ops support to IPoIB Or Gerlitz
2012-09-13 15:56 ` [PATCH net-next V4] IB/ipoib: Add rtnl_link_ops support Or Gerlitz
2012-09-20 20:58 ` David Miller [this message]
2012-09-13 15:56 ` [PATCH iproute2 2/2] iplink: added support for ipoib rtnl link ops Or Gerlitz
2012-09-18 20:07 ` [PATCH net-next V4 0/2] Add rtnl_link_ops support to IPoIB Or Gerlitz
2012-09-18 20:12 ` David Miller
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=20120920.165812.1484686663057692048.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=erezsh@mellanox.co.il \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roland@kernel.org \
/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).