netdev - Re: Dead Config Option STMMAC

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: <86bp8tu3d9.fsf@peer.zerties.org>
Date:	Mon, 23 Aug 2010 10:42:26 +0200
From:	Christian Dietrich <qy03fugy@...d.informatik.uni-erlangen.de>
To:	Peppe CAVALLARO <peppe.cavallaro@...com>
Cc:	Christian Dietrich <qy03fugy@...d.informatik.uni-erlangen.de>,
	"David S. Miller" <davem@...emloft.net>,
	"netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	"vamos-dev\@i4.informatik.uni-erlangen.de" 
	<vamos-dev@...informatik.uni-erlangen.de>
Subject: Re: Dead Config Option STMMAC_ETH?

Peppe CAVALLARO <peppe.cavallaro@...com> writes:

[...]

> There is effort on this driver: currently the driver fully works on
> STM platforms and starts working on ARM (SPEAr Kernels).  The driver
> Kconfig actually depends on the CPU_SUBTYPE_ST40 but it built on x86
> if remove this dependency (just verified).  In the past, I added this
> dependency because the driver was initially tested on ST kernels
> (where we continue to have the CPU_SUBTYPE_ST40) but I can review it
> if you like.

Hm, i think it would be good if this dependency is removed, if it isn't
needed, because then a allyes config would compile test this peace of
code, and it can't die silently with changes around it.

greetz didi
-- 
(λ x . x x) (λ x . x x) -- See how beatiful the lambda is
No documentation is better than bad documentation
-- Das Ausdrucken dieser Mail wird urheberrechtlich verfolgt.
--
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