From: Ben Hutchings <ben@decadent.org.uk>
To: zhuyj <zyjzyj2000@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: ethtool needs a new maintainer
Date: Mon, 04 Jul 2016 20:00:33 +0200 [thread overview]
Message-ID: <1467655233.12588.65.camel@decadent.org.uk> (raw)
In-Reply-To: <CAD=hENfD=cwAidNe1+kspzUtUzwk3QqQE8GWF7zdhrKogPt-=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
On Fri, 2016-07-01 at 10:33 +0800, zhuyj wrote:
> I am interested in this, too.
You didn't say anything about your experience with Linux networking,
and I couldn't find many contributions from you. So you are welcome to
help with ethtool but I've selected John as the maintainer.
Ben.
--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing
anyway.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-04 18:00 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 [this message]
2016-07-04 14:24 ` Jiri Pirko
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=1467655233.12588.65.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=zyjzyj2000@gmail.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).