From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Subbu Seetharaman <subbus@serverengines.com>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND] benet: BladeEngine 10Gb NIC driver
Date: Sun, 2 Nov 2008 07:37:53 -0800 [thread overview]
Message-ID: <20081102153753.GA21617@kroah.com> (raw)
In-Reply-To: <490DA7E3.8040802@garzik.org>
On Sun, Nov 02, 2008 at 08:15:15AM -0500, Jeff Garzik wrote:
> 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?
Anything in the drivers/staging/ directory tree will automatically get
the TAINT_CRAP flag applied to it, so there should not be any need to do
anything else for this.
But, if you want, I can take this, to handle any Kconfig and Makefile
merges that are probably going to be necessary do to me also adding new
drivers in my staging tree. If so, feel free to send me the patch.
thanks,
greg k-h
next prev parent reply other threads:[~2008-11-02 17:54 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
2008-11-02 15:37 ` Greg KH [this message]
-- 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=20081102153753.GA21617@kroah.com \
--to=greg@kroah.com \
--cc=jeff@garzik.org \
--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).