From: David Miller <davem@davemloft.net>
To: catalin.marinas@arm.com
Cc: netdev@vger.kernel.org, steve.glendinning@smsc.com, stable@kernel.org
Subject: Re: [PATCH] smsc911x: Add spinlocks around registers access
Date: Mon, 19 Jul 2010 13:37:30 -0700 (PDT) [thread overview]
Message-ID: <20100719.133730.228932258.davem@davemloft.net> (raw)
In-Reply-To: <20100719123311.21558.37288.stgit@e102109-lin.cambridge.arm.com>
From: Catalin Marinas <catalin.marinas@arm.com>
Date: Mon, 19 Jul 2010 13:42:51 +0100
> On SMP systems, the SMSC911x registers may be accessed by multiple CPUs
> and this seems to put the chip in an inconsistent state. The patch adds
> spinlocks to the smsc911x_reg_read, smsc911x_reg_write,
> smsc911x_rx_readfifo and smsc911x_tx_writefifo functions.
>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Applied to net-next-2.6, thanks.
prev parent reply other threads:[~2010-07-19 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 12:42 [PATCH] smsc911x: Add spinlocks around registers access Catalin Marinas
2010-07-19 20:37 ` David Miller [this message]
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=20100719.133730.228932258.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=catalin.marinas@arm.com \
--cc=netdev@vger.kernel.org \
--cc=stable@kernel.org \
--cc=steve.glendinning@smsc.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).