linux-kernel - Re: Source organization for two drivers sharing coomon code

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: <20070727183558.56c07db4@the-village.bc.nu>
Date:	Fri, 27 Jul 2007 18:35:58 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Subbu Seetharaman" <subbus@...verengines.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Source organization for two drivers sharing coomon code

On Fri, 27 Jul 2007 10:17:29 -0700
"Subbu Seetharaman" <subbus@...verengines.com> wrote:

> 
> 
> What is the recommended way for two drivers to share common code ?
> Our device has two PCI functions and hence two drivers -  NIC and 
> SCSI driver.   The source code for these dirvers will fit under 
> drivers/net and drivers/scsi.  But both drivers share some common 
> code.  If possible, I would like to avoid duplicating the common 
> code under the two driver directories.   Is there any recommened 
> way to organize such common  code ?  Thanks.

What sort of code is shared - historically the cases we have had in the
driver space have mostly been common message passing interfaces to
co-processor type boards (eg I2O or MPT Fusion) and those have lived
under drivers/message/type/...

I don't think there is any hard rule here.

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/