netdev - Re: drivers/net: Kconfig & Makefile cleanup

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] [day] [month] [year] [list]

Message-ID: <1322081889.2282.8.camel@jtkirshe-mobl>
Date:	Wed, 23 Nov 2011 12:58:09 -0800
From:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To:	Ben Hutchings <ben@...adent.org.uk>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: drivers/net: Kconfig & Makefile cleanup

On Mon, 2011-11-21 at 22:51 -0800, Ben Hutchings wrote:
> ou wrote that (some time ago now):
> > As a side cleanup, found that the arcnet, token ring, and PHY
> > Kconfig options were a tri-state option and should have been
> > a bool option.
> 
> How did you decide that?  This seems to be correct for TR, but ARCNET
> and PHYLIB each select some support code that can be built as a module
> (and which has been, in Debian).
> 
> Ben. 

Off the top of my head, I was making the decision based on the other
protocols Kconfig entries.

So does that mean ARCNET could be a module and a driver using ARCNET
would have to be a module as well?

I will take a look at this to come up with a solution, if one has not
been sent out yet.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)