netdev - Re: [patch 12/12] Configure out ethtool support

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 31 Jul 2008 03:43:38 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dwmw2@...radead.org
Cc:	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	thomas.petazzoni@...e-electrons.com, shemminger@...tta.com,
	jeff@...zik.org, netdev@...r.kernel.org, mpm@...enic.com
Subject: Re: [patch 12/12] Configure out ethtool support

From: David Woodhouse <dwmw2@...radead.org>
Date: Thu, 31 Jul 2008 11:39:36 +0100

> We need to be moving towards a situation where people don't _need_ to
> patch the hell out of their kernels to make Linux viable for embedded
> devices. I'm not prepared just assume that 'they will always do so', and
> I'm disappointed to hear Andrew say such a thing. 

It's simple economics, really.

Until they see value in upstream submission, it's always going
to be %100 invested in getting the current product out the door
or the current fire put out.

The odd I2C device hack of the day the do to one revision of their
product is likely never to be submitted upstream.  And these
embedded folks have hundreds of things on that level that they
sort out for each product, and often very little of it is reusable
in the next product.

They don't see the payback for upstreaming this stuff, and for
a lot of cases neither do I.
--
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