From: Jiri Pirko <jpirko@redhat.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: netdev@vger.kernel.org, ralf@linux-mips.org, fubar@us.ibm.com,
andy@greyhouse.net, kaber@trash.net, bprakash@broadcom.com,
JBottomley@parallels.com, robert.w.love@intel.com,
davem@davemloft.net, shemminger@linux-foundation.org,
decot@google.com, mirq-linux@rere.qmqm.pl,
alexander.h.duyck@intel.com, amit.salecha@qlogic.com,
eric.dumazet@gmail.com, therbert@google.com,
paulmck@linux.vnet.ibm.com, laijs@cn.fujitsu.com,
xiaosuo@gmail.com, greearb@candelatech.com,
loke.chetan@gmail.com, linux-mips@linux-mips.org,
linux-scsi@vger.kernel.org, devel@open-fcoe.org,
bridge@lists.linux-foundation.org
Subject: Re: [patch net-next-2.6 v2] net: consolidate and fix ethtool_ops->get_settings calling
Date: Fri, 2 Sep 2011 22:42:41 +0200 [thread overview]
Message-ID: <20110902204239.GA14802@minipsycho> (raw)
In-Reply-To: <1314989161.3419.5.camel@bwh-desktop>
Fri, Sep 02, 2011 at 08:46:01PM CEST, bhutchings@solarflare.com wrote:
>On Fri, 2011-09-02 at 14:26 +0200, Jiri Pirko wrote:
>> This patch does several things:
>> - introduces __ethtool_get_settings which is called from ethtool code and
>> from dev_ethtool_get_settings() as well.
>> - dev_ethtool_get_settings() becomes rtnl wrapper for
>> __ethtool_get_settings()
>[...]
>
>I don't like this locking change. Most other dev_*() functions require
>the caller to hold RTNL, and it will break any OOT module calling
>dev_ethtool_get_settings() without producing any warning at compile
>time. Why not put an ASSERT_RTNL() in it instead?
Hmm. Okay, then I would remove dev_ethtool_get_settings() from
net/core/dev.c and only put __ethtool_get_settings() to
net/core/ethtool.c. Makes more sense to me to have it there...
ASSERT_RTNL woudl be good there as well.
>
>The rest of this looks fine.
>
>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-02 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 19:28 [patch net-next-2.6] net: consolidate and fix ethtool_ops->get_settings calling Jiri Pirko
2011-09-02 12:26 ` [patch net-next-2.6 v2] " Jiri Pirko
2011-09-02 18:46 ` Ben Hutchings
2011-09-02 20:42 ` Jiri Pirko [this message]
2011-09-03 13:34 ` [patch net-next-2.6 v3] " Jiri Pirko
2011-09-03 13:46 ` Ben Hutchings
2011-09-06 3:25 ` Zou, Yi
[not found] ` <5A9BD224CEA58D4CB62235967D650C160A1B7D1C-osO9UTpF0UQd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-09-06 6:52 ` Bhanu Prakash Gollapudi
2011-09-06 12:20 ` Ralf Baechle
2011-09-15 21:33 ` [patch net-next-2.6] " 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=20110902204239.GA14802@minipsycho \
--to=jpirko@redhat.com \
--cc=JBottomley@parallels.com \
--cc=alexander.h.duyck@intel.com \
--cc=amit.salecha@qlogic.com \
--cc=andy@greyhouse.net \
--cc=bhutchings@solarflare.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=kaber@trash.net \
--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=shemminger@linux-foundation.org \
--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).