From: Ben Hutchings <bhutchings@solarflare.com>
To: Jiri Pirko <jpirko@redhat.com>
Cc: amit.salecha@qlogic.com, bridge@lists.linux-foundation.org,
linux-mips@linux-mips.org, devel@open-fcoe.org,
linux-scsi@vger.kernel.org, decot@google.com,
therbert@google.com, robert.w.love@intel.com,
eric.dumazet@gmail.com, fubar@us.ibm.com,
JBottomley@parallels.com, xiaosuo@gmail.com,
paulmck@linux.vnet.ibm.com, alexander.h.duyck@intel.com,
mirq-linux@rere.qmqm.pl, greearb@candelatech.com,
bprakash@broadcom.com, laijs@cn.fujitsu.com,
netdev@vger.kernel.org, ralf@linux-mips.org, davem@davemloft.net,
loke.chetan@gmail.com
Subject: Re: [Bridge] [patch net-next-2.6 v3] net: consolidate and fix ethtool_ops->get_settings calling
Date: Sat, 03 Sep 2011 14:46:47 +0100 [thread overview]
Message-ID: <1315057614.3092.160.camel@deadeye> (raw)
In-Reply-To: <20110903133428.GA2821@minipsycho>
On Sat, 2011-09-03 at 15:34 +0200, Jiri Pirko wrote:
> This patch does several things:
> - introduces __ethtool_get_settings which is called from ethtool code and
> from drivers as well. Put ASSERT_RTNL there.
> - dev_ethtool_get_settings() is replaced by __ethtool_get_settings()
> - changes calling in drivers so rtnl locking is respected. In
> iboe_get_rate was previously ->get_settings() called unlocked. This
> fixes it. Also prb_calc_retire_blk_tmo() in af_packet.c had the same
> problem. Also fixed by calling __dev_get_by_index() instead of
> dev_get_by_index() and holding rtnl_lock for both calls.
> - introduces rtnl_lock in bnx2fc_vport_create() and fcoe_vport_create()
> so bnx2fc_if_create() and fcoe_if_create() are called locked as they
> are from other places.
> - use __ethtool_get_settings() in bonding code
>
> Signed-off-by: Jiri Pirko <jpirko@redhat.com>
Reviewed-by: Ben Hutchings <bhutchings@solarflare.com> [except FCoE bits]
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-09-03 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 19:28 [Bridge] [patch net-next-2.6] net: consolidate and fix ethtool_ops->get_settings calling Jiri Pirko
2011-09-02 12:26 ` [Bridge] [patch net-next-2.6 v2] " Jiri Pirko
2011-09-02 18:46 ` Ben Hutchings
2011-09-02 20:42 ` Jiri Pirko
2011-09-03 13:34 ` [Bridge] [patch net-next-2.6 v3] " Jiri Pirko
2011-09-03 13:46 ` Ben Hutchings [this message]
2011-09-06 3:25 ` Zou, Yi
2011-09-06 6:52 ` Bhanu Prakash Gollapudi
2011-09-06 12:20 ` Ralf Baechle
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=1315057614.3092.160.camel@deadeye \
--to=bhutchings@solarflare.com \
--cc=JBottomley@parallels.com \
--cc=alexander.h.duyck@intel.com \
--cc=amit.salecha@qlogic.com \
--cc=bprakash@broadcom.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=decot@google.com \
--cc=devel@open-fcoe.org \
--cc=eric.dumazet@gmail.com \
--cc=fubar@us.ibm.com \
--cc=greearb@candelatech.com \
--cc=jpirko@redhat.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loke.chetan@gmail.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=ralf@linux-mips.org \
--cc=robert.w.love@intel.com \
--cc=therbert@google.com \
--cc=xiaosuo@gmail.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).