From: Jeff Garzik <jeff@garzik.org>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: NetDev <netdev@vger.kernel.org>, David Miller <davem@davemloft.net>
Subject: Re: ethtool maintenance
Date: Mon, 15 Nov 2010 14:16:41 -0500 [thread overview]
Message-ID: <4CE18719.6080604@garzik.org> (raw)
In-Reply-To: <1289832387.2586.10.camel@bwh-desktop>
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
On 11/15/2010 09:46 AM, Ben Hutchings wrote:
> 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.
I've attached an mbox.
In the short term, there is no need to wait, I can simply publish 'git
pull' requests from you, and push a release out to SF.
I would recommend moving the tarball release area away from SF in the
long term; SF is really going downhill.
Jeff
[-- Attachment #2: mbox.bz2 --]
[-- Type: application/x-bzip, Size: 23028 bytes --]
prev parent reply other threads:[~2010-11-15 19:16 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
2010-11-15 19:16 ` Jeff Garzik [this message]
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=4CE18719.6080604@garzik.org \
--to=jeff@garzik.org \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).