From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCH 0/4] batman-adv: ethtool code cleanup
Date: Sat, 1 Apr 2017 14:47:02 +0200 [thread overview]
Message-ID: <20170401124706.18257-1-sven@narfation.org> (raw)
Hi,
Philippe Reynes sent in a patch [1] to convert the get_settings stuff to
the new ethtool link_ksettings api. I've therefore asked Marek (original
author of the ethtool stubs) whether the code is still needed for
something.
He couldn't remember anything about it. This was therefore a good
opportunity to completely get rid of the code - instead of converting
not useful code to the new api.
Kind regards,
Sven
[1] https://patchwork.open-mesh.org/patch/16982/
Sven Eckelmann (4):
batman-adv: Use ethtool helper to get link status
batman-adv: Remove ethtool msglevel functions
batman-adv: Remove ethtool .get_settings stub
batman-adv: Group ethtool related code together
net/batman-adv/soft-interface.c | 229 ++++++++++++++++------------------------
1 file changed, 92 insertions(+), 137 deletions(-)
--
2.11.0
next reply other threads:[~2017-04-01 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 12:47 Sven Eckelmann [this message]
2017-04-01 12:47 ` [B.A.T.M.A.N.] [PATCH 1/4] batman-adv: Use ethtool helper to get link status Sven Eckelmann
2017-04-01 12:47 ` [B.A.T.M.A.N.] [PATCH 2/4] batman-adv: Remove ethtool msglevel functions Sven Eckelmann
2017-04-01 12:47 ` [B.A.T.M.A.N.] [PATCH 3/4] batman-adv: Remove ethtool .get_settings stub Sven Eckelmann
2017-04-01 12:47 ` [B.A.T.M.A.N.] [PATCH 4/4] batman-adv: Group ethtool related code together Sven Eckelmann
2017-04-01 15:35 ` [B.A.T.M.A.N.] [PATCH 0/4] batman-adv: ethtool code cleanup Marek Lindner
2017-04-03 16:12 ` Simon Wunderlich
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=20170401124706.18257-1-sven@narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.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