From: David Miller <davem@davemloft.net>
To: manish.chopra@qlogic.com
Cc: netdev@vger.kernel.org, umgwanakikbuti@gmail.com,
Dept-GELinuxNICDev@qlogic.com
Subject: Re: [PATCH net 0/2] netxen: Bug fixes.
Date: Tue, 30 Sep 2014 16:23:15 -0400 (EDT) [thread overview]
Message-ID: <20140930.162315.1445819984262897387.davem@davemloft.net> (raw)
In-Reply-To: <1412063796-25959-1-git-send-email-manish.chopra@qlogic.com>
From: Manish Chopra <manish.chopra@qlogic.com>
Date: Tue, 30 Sep 2014 03:56:34 -0400
> This series fixes some TX specific issues.
> * Move spin_lock(tx_clean_lock) in down path to fix
> atomic sleep bug (Reported by Mike Galbraith).
> * Fix hang in interface down while running traffic.
>
> Please consider applying this to 'net'.
Series applied, thanks.
prev parent reply other threads:[~2014-09-30 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 7:56 [PATCH net 0/2] netxen: Bug fixes Manish Chopra
2014-09-30 7:56 ` [PATCH net 1/2] netxen: Fix BUG "sleeping function called from invalid context" Manish Chopra
2014-09-30 7:56 ` [PATCH net 2/2] netxen: Fix bug in Tx completion path Manish Chopra
2014-09-30 20:23 ` 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=20140930.162315.1445819984262897387.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Dept-GELinuxNICDev@qlogic.com \
--cc=manish.chopra@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=umgwanakikbuti@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).