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]

Date:	Fri, 27 Jul 2007 13:12:21 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
CC:	Subbu Seetharaman <subbus@...verengines.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Source organization for two drivers sharing coomon code

Jan Engelhardt wrote:
> On Jul 27 2007 10:17, Subbu Seetharaman wrote:
> 
>>What is the recommended way for two drivers to share common code ?
>><snip>...The source code for these dirvers will fit under 
>>drivers/net and drivers/scsi.  But both drivers share some common 
>>code.

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

Where would the common code live, in such a case?  Would you just pick 
one of the two locations at random, or put it in drivers/misc or maybe lib?

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