netdev - Re: [PATCH] Reduce locking in TX path of forcedth driver

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

Message-ID: <476DC460.6030701@garzik.org>
Date:	Sat, 22 Dec 2007 21:13:52 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Tom Herbert <therbert@...gle.com>
CC:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	netdev@...r.kernel.org, Ayaz Abdulla <aabdulla@...dia.com>
Subject: Re: [PATCH] Reduce locking in TX path of forcedth driver

Tom Herbert wrote:
> 
>     (Tom, you failed to CC the maintainer at NVIDIA, please fix...)
> 
>  
> Jeff,
>  
> Please pardon my naivety, but how would determine who the maintainer at 
> NVDIA is?  The MAINTAINERS file lists an Nvidia maintainer only for the 
> framebuffer driver, and I don't see this specified in the source file.

In general, you want to check with

	git log drivers/net/forcedeth.c

in addition to MAINTAINERS, to see who is actively working on the driver.

In this case, the original authors are largely idle (though still 
respond to emails), and NVIDIA has been doing most of the maintenance 
for the past year or more.

MAINTAINERS certainly wants fixing though, if it doesn't reflect the 
current situation.

	Jeff



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