All of lore.kernel.org
 help / color / mirror / Atom feed
From: Debashis Dutt <ddutt@Brocade.COM>
To: David Miller <davem@davemloft.net>,
	"debdut@gmail.com" <debdut@gmail.com>
Cc: "jirislaby@gmail.com" <jirislaby@gmail.com>,
	Rasesh Mody <rmody@Brocade.COM>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: bna: potential null dereference
Date: Sun, 12 Sep 2010 15:41:53 -0700	[thread overview]
Message-ID: <F363E7AC84E1B646A0358B281A46F4AEA9C0AE4D03@HQ1-EXCH03.corp.brocade.com> (raw)
In-Reply-To: <20100912.153805.226772440.davem@davemloft.net>


-----Original Message-----
From: David Miller [mailto:davem@davemloft.net] 
Sent: Sunday, September 12, 2010 3:38 PM
To: debdut@gmail.com
Cc: jirislaby@gmail.com; Debashis Dutt; Rasesh Mody; netdev@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: bna: potential null dereference

From: Debashis Dutt <debdut@gmail.com>
Date: Sun, 12 Sep 2010 15:35:41 -0700

> A patch is on the way by tomorrow. BTW, this is just an unnecessary
> check that should be removed and not a NULL de-reference.

I've already made a fix in the net-next-2.6 tree.

You should send me fixes like this when you have them and are
reasonably confident of the change, which for something like
this should have been a day or two at most, not a week later.


Sure David. 

Apologize for the delay again. Had too many things on my plate.
Would be more prompt hence forth.

Thanks
--Debashis

      reply	other threads:[~2010-09-12 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-04 12:59 bna: potential null dereference Jiri Slaby
2010-09-12 19:02 ` David Miller
     [not found]   ` <AANLkTi=cZyLYJac8b8MsyAA4HitCvpD3NaH7nifzHDLw@mail.gmail.com>
2010-09-12 22:38     ` David Miller
2010-09-12 22:41       ` Debashis Dutt [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=F363E7AC84E1B646A0358B281A46F4AEA9C0AE4D03@HQ1-EXCH03.corp.brocade.com \
    --to=ddutt@brocade.com \
    --cc=davem@davemloft.net \
    --cc=debdut@gmail.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rmody@Brocade.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.