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: <alpine.LFD.2.00.0906111605060.31536@xanadu.home>
Date:	Thu, 11 Jun 2009 16:24:05 -0400 (EDT)
From:	Nicolas Pitre <nico@....org>
To:	Ben Hutchings <bhutchings@...arflare.com>
Cc:	mfuzzey@...il.com, netdev@...r.kernel.org
Subject: Re: [RFC PATCH] Ethtool style in kernel network driver configuration.

On Thu, 11 Jun 2009, Ben Hutchings wrote:

> On Thu, 2009-06-11 at 15:08 -0400, Nicolas Pitre wrote:
> [...]
> > > Please note, I'm talking about an init script -
> > > which you surely must have - not an initramfs, which I recognise is
> > > optional and unnecessary for most embedded systems.
> > 
> > An init script is already a luxury for some systems.
> 
> And so is an Ethernet port.  Instead of talking about hypotheticals, why
> not talk about the system you need this workaround for?

Look, I personally do not need this.  And I'm rather tired arguing with 
you.  Your shortsightedness and refusal for accommodation about needs 
that aren't yours is representative of the main reason why there is 
still a disconnect between mainline people and embedded people.  If you 
can't admit it then I've failed my attempt at bridging the gap.

The issue was discussed, people objected to driver kirks already, then I 
proposed this solution to which Davem agreed if it was done cleanly and 
maintained. And here it is under the form of an actual patch. So far 
you're the only one who just can't accept that compromise.  If your 
opposition -- which so far has nothing to do with the actual 
implementation but rather on the principle -- is not overruled by others 
then the embedded disconnect, of which this is only a tiny part of, has 
no hope of ever vanishing.

Have a good day.

Nicolas
--
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