From: "Chris Friesen" <cfriesen@nortel.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Subbu Seetharaman <subbus@serverengines.com>,
linux-kernel@vger.kernel.org
Subject: Re: Source organization for two drivers sharing coomon code
Date: Fri, 27 Jul 2007 13:12:21 -0600 [thread overview]
Message-ID: <46AA4395.3050907@nortel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707272102070.16356@fbirervta.pbzchgretzou.qr>
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
next prev parent reply other threads:[~2007-07-27 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 17:17 Subbu Seetharaman
2007-07-27 17:35 ` Alan Cox
2007-07-27 19:03 ` Jan Engelhardt
2007-07-27 19:12 ` Chris Friesen [this message]
2007-07-27 19:34 ` Jan Engelhardt
2007-07-28 2:42 Subbu Seetharaman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46AA4395.3050907@nortel.com \
--to=cfriesen@nortel.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=subbus@serverengines.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®