From: David Miller <davem@davemloft.net>
To: ben@decadent.org.uk
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-2.6] 3c59x: Remove incorrect locking; correct documented lock hierarchy
Date: Wed, 01 Sep 2010 17:37:36 -0700 (PDT) [thread overview]
Message-ID: <20100901.173736.190380817.davem@davemloft.net> (raw)
In-Reply-To: <1283378907.5323.287.camel@localhost>
From: Ben Hutchings <ben@decadent.org.uk>
Date: Wed, 01 Sep 2010 23:08:27 +0100
> I think this is safe after all because ethtool and MII ioctls are all
> serialised by the RTNL.
Well since you said that there was a regression that you're unable
to reproduce, I was trying to find a probably cause for it :-)
I think you should work to resolve that report, and resend this
locking patch once that is sorted out.
Thanks.
next prev parent reply other threads:[~2010-09-02 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 0:15 [PATCH net-2.6] 3c59x: Remove incorrect locking; correct documented lock hierarchy Ben Hutchings
2010-09-01 21:38 ` David Miller
2010-09-01 21:47 ` Ben Hutchings
2010-09-01 22:08 ` Ben Hutchings
2010-09-02 0:37 ` David Miller [this message]
2010-09-02 0:42 ` Ben Hutchings
2010-09-02 1:02 ` 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=20100901.173736.190380817.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ben@decadent.org.uk \
--cc=netdev@vger.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).