From: Thomas Martitz <thomas.martitz@hhi.fraunhofer.de>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Preferred method for configuration
Date: Tue, 13 Aug 2013 14:13:34 +0200 [thread overview]
Message-ID: <520A22EE.8040006@hhi.fraunhofer.de> (raw)
In-Reply-To: <20130808090111.241a2043@nehalam.linuxnetplumber.net>
Am 08.08.2013 18:01, schrieb Stephen Hemminger:
> On Thu, 08 Aug 2013 07:56:04 +0200
> Thomas Martitz <thomas.martitz@hhi.fraunhofer.de> wrote:
>
>> Resent with list in CC.
>>
>> Am 08.08.2013 07:41, schrieb Joe Perches:
>>> On Thu, 2013-08-08 at 07:32 +0200, Thomas Martitz wrote:
>>>> Hello,
>>>>
>>>> I'm developing a NIC driver and currently export some custom
>>>> configuration settings and actions (e.g. enabling a loopback mode) via
>>>> sysfs.
>>>
>>> Is there some reason you don't want to use ethtool?
>>>
>>>
>>
>> It doesn't allow for custom settings does it? For standards stuff I'm
>> sure going to use ethtool.
>
> Any feature "special to my driver" is sure to meet stiff resistance
> from the kernel developers. Special features make it impossible for generic
> configuration in distributions and by management layers.
>
What about features that are really unique to the device?
Best regards.
prev parent reply other threads:[~2013-08-13 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 5:32 Preferred method for configuration Thomas Martitz
2013-08-08 5:41 ` Joe Perches
2013-08-08 5:56 ` Thomas Martitz
2013-08-08 9:44 ` Ben Hutchings
2013-08-08 16:01 ` Stephen Hemminger
2013-08-13 12:13 ` Thomas Martitz [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=520A22EE.8040006@hhi.fraunhofer.de \
--to=thomas.martitz@hhi.fraunhofer.de \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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