All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Ben Hutchings <ben@decadent.org.uk>, netdev <netdev@vger.kernel.org>
Subject: Re: ethtool needs a new maintainer
Date: Mon, 4 Jul 2016 16:24:55 +0200	[thread overview]
Message-ID: <20160704142455.GH2325@nanopsycho.orion> (raw)
In-Reply-To: <20160627135146.GB6864@tuxdriver.com>

Mon, Jun 27, 2016 at 03:51:47PM CEST, linville@tuxdriver.com wrote:
>On Sun, Jun 26, 2016 at 06:11:41PM +0200, Ben Hutchings wrote:
>> I've become steadily less enthusiastic and less responsive as a
>> maintainer over the past year or so.  I no longer work on networking
>> regularly, so it takes a lot more time to get into the right state of
>> mind to think about ethtool code, while I have other demands on my time
>> that tend to take priority.
>> 
>> So, I would like to find a new maintainer to take over as soon as
>> possible.  Ideally the new maintainer would have previous contributions
>> to ethtool and an existing account on kernel.org so that they can push
>> to the git repository and the home page.  But neither of those is
>> essential.  Please reply if you're interested.
>
>I would like to take this responsibility. My previous contributions
>to ethtool are meager, but I think my skills and interests are suited
>to the task.  Plus, I already have a kernel.org account... :-)
>
>> I was thinking of adding a TODO file to the repository, but it's really
>> for the new maintainer to decide what to do.  So here's my list as a
>> suggestion:
>> 
>> * Add regression test coverage for all sub-commands with complex logic
>> 
>> * Internationalise output and error messages
>> 
>> * Build a libethtool that handles all the API quirks and fallbacks for
>>   old kernel versions.  This might help people writing language
>>   bindings or other utilities that use the ethtool API.
>> 
>> * Provide a 'cleaned up' ethtool (under some other name) that has:
>>   - More conventional sub-command syntax, i.e. no '-'/'--' prefix
>>   - More consistent output formatting
>
>That seems like a reasonable start for a TODO list. I'll bet there
>are a few people out there with other suggestions as well...?

Before that, I would like to see ethtool migrate to use generic
netlink. Then, the new tool would be needed anyway, should exist within
iproute2 package and have similar command line syntax.

I have some ideas about the gennetlink ethtool, have to find some time
to implement some initial part of it.

  parent reply	other threads:[~2016-07-04 14:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26 15:59 ethtool 4.6 released Ben Hutchings
2016-06-26 16:11 ` ethtool needs a new maintainer Ben Hutchings
2016-06-27 13:51   ` John W. Linville
2016-06-30 18:15     ` John W. Linville
2016-06-30 19:27       ` Jorge Alberto Garcia
2016-06-30 19:32         ` Ben Hutchings
     [not found]           ` <CAPfrtUce=xzHystAoMRth4HEKhZtSj629f07R-t-dsq5=9q0-g@mail.gmail.com>
     [not found]             ` <CAPfrtUeQuKiHAejZmhYORUh+1ZrD0QnAJ4PszRi++O-+dindoA@mail.gmail.com>
     [not found]               ` <CAPfrtUeYwu8hj_ZNvp97_=v1hFuNBNPTG+Rfct644aTRh=JBog@mail.gmail.com>
2016-06-30 21:51                 ` John W. Linville
2016-07-04 17:38                 ` Ben Hutchings
2016-06-30 22:12       ` John Fastabend
2016-07-01 18:31         ` Andy Gospodarek
2016-07-01 19:33           ` David Miller
     [not found]       ` <CAD=hENfD=cwAidNe1+kspzUtUzwk3QqQE8GWF7zdhrKogPt-=A@mail.gmail.com>
2016-07-04 18:00         ` Ben Hutchings
2016-07-04 14:24     ` Jiri Pirko [this message]
2016-07-04 17:18     ` Ben Hutchings
2016-07-05 15:58       ` John W. Linville

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=20160704142455.GH2325@nanopsycho.orion \
    --to=jiri@resnulli.us \
    --cc=ben@decadent.org.uk \
    --cc=linville@tuxdriver.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.