From: "Subbu Seetharaman" <subbus@serverengines.com>
To: "Jeff Garzik" <jeff@garzik.org>, "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: Mon, 03 Nov 2008 04:25:12 -0800 [thread overview]
Message-ID: <20081103122512.06063fc9@mailhost.serverengines.com> (raw)
In-Reply-To: 490DA7E3.8040802@garzik.org
If we could get more specific feedback about the areas that require cleanup, we can take care of them quickly.
Since the last posting, we have brought up the driver in a PPC system and fixed some endianness issues. As soon as I have some specific feedback, we can update the driver with these fixes as well.
Please let me know as soon as the driver is in the staging area.
Thanks.
Subbu
----- Original Message -----
From: Jeff Garzik [mailto:jeff@garzik.org]
To: Subbu Seetharaman [mailto:subbus@serverengines.com], Greg KH [mailto:greg@kroah.com]
Cc: netdev@vger.kernel.org, LKML [mailto:linux-kernel@vger.kernel.org]
Sent: Sun, 02 Nov 2008 05:15:15 -0800
Subject: Re: [RESEND] benet: BladeEngine 10Gb NIC driver
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
--
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
___________________________________________________________________________________
This message, together with any attachment(s), contains confidential and proprietary information of
ServerEngines Corporation and is intended only for the designated recipient(s) named above. Any unauthorized
review, printing, retention, copying, disclosure or distribution is strictly prohibited. If you are not the
intended recipient of this message, please immediately advise the sender by reply email message and
delete all copies of this message and any attachment(s). Thank you.
next reply other threads:[~2008-11-03 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 12:25 Subbu Seetharaman [this message]
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
[not found] <20080916090021.c4a58c42@mailhost.serverengines.com>
2008-11-02 13:15 ` Jeff Garzik
2008-11-02 15:37 ` 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=20081103122512.06063fc9@mailhost.serverengines.com \
--to=subbus@serverengines.com \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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
all inboxes | Powered by JetHome®