From: Ben Hutchings <bhutchings@solarflare.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: NetDev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Peter Martuccelli <peterm@redhat.com>
Subject: Re: ethtool maintenance
Date: Mon, 15 Nov 2010 14:46:27 +0000 [thread overview]
Message-ID: <1289832387.2586.10.camel@bwh-desktop> (raw)
In-Reply-To: <1289658614.2816.105.camel@localhost>
On Sat, 2010-11-13 at 14:30 +0000, Ben Hutchings wrote:
> On Sat, 2010-11-13 at 03:45 -0500, Jeff Garzik wrote:
> > So, a recent emergency surgery has really set me back, work-wise.
> > ethtool [the userspace utility] 2.6.36 is still not out, and personally
> > it remains a third or fourth priority.
> >
> > While it's likely that I could get back to ethtool's patch queue next
> > week, it continues to be low man on the totem pole. Seems only fair to
> > see if anyone else is interested in maintaining it.
> >
> > I emailed Ben Hutchings privately about this, but haven't heard back, so
> > I thought I'd go ahead and email the list.
> >
> > Anyone interested?
>
> I am interested, but will need to clear it with my boss before making
> such a commitment.
OK, this is fine. Are there any patches waiting other than mine and
these?
http://patchwork.ozlabs.org/patch/67662/
http://patchwork.ozlabs.org/patch/68237/
http://patchwork.ozlabs.org/patch/69155/
I'll need to sort out my kernel.org account before I can publish a git
tree.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-11-15 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 8:45 ethtool maintenance Jeff Garzik
2010-11-13 14:30 ` Ben Hutchings
2010-11-15 14:46 ` Ben Hutchings [this message]
2010-11-15 19:16 ` 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=1289832387.2586.10.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=peterm@redhat.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