From: Prashant Sreedharan <prashant@broadcom.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <mchan@broadcom.com>,
<peter@hurleysoftware.com>,
Prashant Sreedharan <prashant@broadcom.com>
Subject: [PATCH net 0/3]tg3: synchronize_irq() should be called without taking locks
Date: Tue, 13 Jan 2015 22:30:39 -0800 [thread overview]
Message-ID: <1421217039-11689-1-git-send-email-prashant@broadcom.com> (raw)
Prashant Sreedharan (3):
tg3_timer() should grab tp->lock before checking for tp->irq_sync
tg3_reset_task() needs to use rtnl_lock to synchronize
Release tp->lock before invoking synchronize_irq()
Our QA team is validating this patch set, we need few days before merging
drivers/net/ethernet/broadcom/tg3.c | 23 ++++++++++++++++++++---
1 files changed, 20 insertions(+), 3 deletions(-)
next reply other threads:[~2015-01-14 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 6:30 Prashant Sreedharan [this message]
2015-01-14 15:57 ` [PATCH net 0/3]tg3: synchronize_irq() should be called without taking locks Peter Hurley
2015-01-14 19:04 ` Prashant Sreedharan
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=1421217039-11689-1-git-send-email-prashant@broadcom.com \
--to=prashant@broadcom.com \
--cc=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=peter@hurleysoftware.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).