netdev - Re: [RFC PATCH] Ethtool style in kernel network driver configuration.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A334E7A.5020805@gmail.com>
Date:	Sat, 13 Jun 2009 09:00:10 +0200
From:	Martin Fuzzey <mfuzzey@...il.com>
To:	David Miller <davem@...emloft.net>
CC:	bhutchings@...arflare.com, nico@....org, netdev@...r.kernel.org
Subject: Re: [RFC PATCH] Ethtool style in kernel network driver configuration.

David Miller wrote:
> I don't expect anyone to be required to read a data-sheet just to
> prevent some link mode settings.
>
> If the driver isn't clean enough to make a change like that easy,
> that's a bug.
>
> This is just a scarecrow argument.
>   
Ok if you like.

But please reply to the rest of that message, in particular explain why,
having publicly stated you would accept an implementation of Nicolas'
idea, you are now back pedaling. I'm quite prepared to be told that the
code itself is not good enough yet (with indications of how to improve
it) but we're not even discussing the code.

The impression (and I sincerely hope I am wrong) this gives me is that
when you accepted the idea in principle you didn't think anyone would
actually step up and write the code [presumably because us embedded
people are too busy working on our quick hacks]. Well I did and now I'm
calling upon you to keep your word.

At the end of the day you are the networking maintainer and I'm a no
name so you can tell me to go jump in the lake. But think a little about
the message that would send first. To the best of my knowledge I
respected the linux development process by discussing first and
apparently reaching a consensus - it's not like I jumped in with a chunk
of code demanding it be merged. If I misunderstood the process please
tell me too.

Martin

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html