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: <Pine.LNX.4.64.0707272102070.16356@fbirervta.pbzchgretzou.qr>
Date:	Fri, 27 Jul 2007 21:03:05 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Subbu Seetharaman <subbus@...verengines.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Source organization for two drivers sharing coomon code


On Jul 27 2007 10:17, Subbu Seetharaman 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.

You could create (in total) three modules, e.g. my-common.ko,
my-net.ko and my-scsi.ko, of which the latter two use functions from the first.


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