netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: yuvalmin@broadcom.com
Cc: netdev@vger.kernel.org, ariele@broadcom.com, eilong@broadcom.com
Subject: Re: [PATCH net] bnx2x: Prevent NULL pointer dereference in kdump
Date: Thu, 25 Apr 2013 04:02:05 -0400 (EDT)	[thread overview]
Message-ID: <20130425.040205.1470520940896024864.davem@davemloft.net> (raw)
In-Reply-To: <1366635183-9541-1-git-send-email-yuvalmin@broadcom.com>

From: "Yuval Mintz" <yuvalmin@broadcom.com>
Date: Mon, 22 Apr 2013 15:53:03 +0300

> After verifying that by re-arranging the order by which interrupts' resource
> were allocated and requested, we could no longer re-produce the Spurious
> interrupt issue, we've dropped the spurious flag.

I told you :-)

Applied, thanks.

      reply	other threads:[~2013-04-25  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 12:53 [PATCH net] bnx2x: Prevent NULL pointer dereference in kdump Yuval Mintz
2013-04-25  8:02 ` 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=20130425.040205.1470520940896024864.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ariele@broadcom.com \
    --cc=eilong@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=yuvalmin@broadcom.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).