From: Jeff Garzik <jeff@garzik.org>
To: Subbu Seetharaman <subbus@serverengines.com>, Greg KH <greg@kroah.com>
Cc: netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND] benet: BladeEngine 10Gb NIC driver
Date: Sun, 02 Nov 2008 08:15:15 -0500 [thread overview]
Message-ID: <490DA7E3.8040802@garzik.org> (raw)
In-Reply-To: <20080916090021.c4a58c42@mailhost.serverengines.com>
Subbu Seetharaman wrote:
> Jeff,
>
> It is more than two months since the benet driver patch was made available as a single file as suggeted by you :
>
> ftp://ftp.serverengines.com/0001.benet.patch
>
> I have not seen this applied. Is there any reason for not applying this patch ? Do you want a patch against the latest git tree ?
The overall consensus at this year's Linux Kernel Summit was that this
driver still needs a lot of cleanup, so I'm gonna try an experiment and
stick this in the staging tree (currently jgarzik/netdev-2.6.git#benet).
Greg, do I need to do anything beyond simply putting it into the
directory? Do I need to add some code to taint, perhaps?
Jeff
next prev parent reply other threads:[~2008-11-02 13:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 9:00 [RESEND] benet: BladeEngine 10Gb NIC driver Subbu Seetharaman
2008-11-02 13:15 ` Jeff Garzik [this message]
2008-11-02 15:37 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2008-11-03 12:25 Subbu Seetharaman
2008-11-03 19:36 ` Greg KH
2008-11-03 19:52 ` Jeff Garzik
2008-11-03 19:55 ` Greg KH
2008-11-03 20:19 ` Greg KH
2008-11-03 20:42 ` Jeff Garzik
2008-11-03 20:46 ` Greg KH
2008-11-03 20:55 ` Jeff Garzik
2008-11-03 21:40 ` Greg KH
2008-11-04 10:41 ` Ilpo Järvinen
2008-11-05 5:02 ` Greg KH
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=490DA7E3.8040802@garzik.org \
--to=jeff@garzik.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=subbus@serverengines.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).