netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: rajesh.borundia@qlogic.com
Cc: netdev@vger.kernel.org, Dept-HSGLinuxNICDev@qlogic.com
Subject: Re: [PATCH net v2 0/2] qlcnic fixes
Date: Thu, 10 Mar 2016 16:16:35 -0500 (EST)	[thread overview]
Message-ID: <20160310.161635.432267926229064181.davem@davemloft.net> (raw)
In-Reply-To: <1457422798-17981-1-git-send-email-rajesh.borundia@qlogic.com>

From: Rajesh Borundia <rajesh.borundia@qlogic.com>
Date: Tue, 8 Mar 2016 02:39:56 -0500

> This series adds following fixes.
> 
> o While processing mailbox if driver gets a spurious mailbox
>   interrupt it leads into premature completion of a next
>   mailbox request. Added a guard against this by checking current
>   state of mailbox and ignored spurious interrupt.
>   Added a stats counter to record this condition.
> 
> v2:
> 
> o Added patch that removes usage of atomic_t as we are not implemeting
>   atomicity by using atomic_t value.
> 
> Please apply these fixes to net.

As explained in other list postings, 'net' is basically closed for this
release cycle, so I applied this series to 'net-next'.

Let me know if you'd like me to therefore queue these changes up for
-stable.

Thanks.

  parent reply	other threads:[~2016-03-10 21:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08  7:39 [PATCH net v2 0/2] qlcnic fixes Rajesh Borundia
2016-03-08  7:39 ` [PATCH net v2 1/2] qlcnic: Remove unnecessary usage of atomic_t Rajesh Borundia
2016-03-08  7:39 ` [PATCH net v2 2/2] qlcnic: Fix mailbox completion handling during spurious interrupt Rajesh Borundia
2016-03-10 21:16 ` David Miller [this message]
2016-03-11  6:40   ` [PATCH net v2 0/2] qlcnic fixes Rajesh Borundia
2016-03-11 16:41     ` 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=20160310.161635.432267926229064181.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Dept-HSGLinuxNICDev@qlogic.com \
    --cc=netdev@vger.kernel.org \
    --cc=rajesh.borundia@qlogic.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).