From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-2.6 1/2] cnic: Prevent status block race conditions with hardware
Date: Wed, 02 Mar 2011 16:00:12 -0800 (PST) [thread overview]
Message-ID: <20110302.160012.35056753.davem@davemloft.net> (raw)
In-Reply-To: <1299106850-23645-1-git-send-email-mchan@broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Wed, 2 Mar 2011 15:00:49 -0800
> The status block index is used to acknowledge interrupt events and must
> be read before checking for the interrupt events, so we need to add rmb()
> to guarantee that.
>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
Applied.
prev parent reply other threads:[~2011-03-02 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 23:00 [PATCH net-2.6 1/2] cnic: Prevent status block race conditions with hardware Michael Chan
2011-03-02 23:00 ` [PATCH net-2.6 2/2] cnic: Fix lost interrupt on bnx2x Michael Chan
2011-03-03 0:00 ` David Miller
2011-03-03 0:00 ` 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=20110302.160012.35056753.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@broadcom.com \
--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).