netdev - Re: [PATCH net-next] Sweep away N/A fw_version dustbunnies from the .get

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: <4ECC23AB.5060808@hp.com>
Date:	Tue, 22 Nov 2011 14:35:23 -0800
From:	Rick Jones <rick.jones2@...com>
To:	Francois Romieu <romieu@...zoreil.com>
CC:	Rick Jones <raj@...dy.cup.hp.com>, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] Sweep away N/A fw_version dustbunnies from the
 .get_drvinfo routine of a number of drivers

On 11/22/2011 02:22 PM, Francois Romieu wrote:
> Rick Jones<raj@...dy.cup.hp.com>  :
> [...]
>> Per discussion with Ben Hutchings and David Miller, go through and
>> remove assignments of "N/A" to fw_version in various drivers'
>> .get_drvinfo routines.  While there clean-up some use of bare
>> constants and such.
>
> Any reason why drivers/net/ethernet/realtek/r8169.c is left in the
> cold ?

No specific reason.  I might not have caught it with my find/grep, or it 
might not have been built in my build environment - after I cloned 
net-next, I brought the .config file from my 64-bit ubuntu virtual 
system to the BE (been bringing it along rather like sourdough starter), 
did a make oldconfig, took all the defaults, did a "make" and then only 
modified those files for which I found the "N/A" in the .c file and 
which had a corresponding .o - that way I "knew" that my changes would 
at least be compiled subsequently and so minimizing the chances of 
incurring davem's wrath by sending him non-compiling code :)

rick jones
--
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