From: Divy Le Ray <divy@chelsio.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jeff Garzik <jeff@garzik.org>,
pradeep singh <pradeep.rautela@gmail.com>,
trivial@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2.6.22-rc5] cxgb2: handle possible NULL pointer dereferencing, take 2
Date: Tue, 26 Jun 2007 09:24:29 -0700 [thread overview]
Message-ID: <46813DBD.3060803@chelsio.com> (raw)
In-Reply-To: <20070625163015.175d15c0.akpm@linux-foundation.org>
Andrew Morton wrote:
>
> On Mon, 25 Jun 2007 19:14:05 -0400
> Jeff Garzik <jeff@garzik.org> wrote:
>
> > Andrew Morton wrote:
> > > The chelsio driver is assuming that pci_device_id.driver_data has been
> > > initialised to the board index, but I am unable to locate anywhere
> where
> > > that initialisation actually happens.
> >
> > It's hidden inside the CH_DEVICE() initializer-helper macro.
> >
>
> oic.
>
> Does this driver still have a maintainer, or is it now a "community"
> driver (giggle) ?
>
I follow the driver's changes. No new features going in anymore, and it
has been quite stable.
The activity is low.
Cheers,
Divy
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2007-06-26 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 12:53 [PATCH v2.6.22-rc5] cxgb2: handle possible NULL pointer dereferencing, take 2 pradeep singh
2007-06-21 13:00 ` pradeep singh
2007-06-21 13:18 ` pradeep singh
2007-06-23 16:54 ` Andrew Morton
2007-06-25 5:46 ` pradeep singh
2007-06-25 22:34 ` Andrew Morton
2007-06-25 23:14 ` Jeff Garzik
2007-06-25 23:30 ` Andrew Morton
2007-06-25 23:32 ` Jeff Garzik
2007-06-26 16:24 ` Divy Le Ray [this message]
2007-06-25 23:15 ` Jeff Garzik
2007-06-26 0:38 ` Stephen Hemminger
2007-06-27 6:30 ` Jeff Garzik
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=46813DBD.3060803@chelsio.com \
--to=divy@chelsio.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=pradeep.rautela@gmail.com \
--cc=trivial@kernel.org \
/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).