mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Subbu Seetharaman" <subbus@serverengines.com>
To: linux-kernel@vger.kernel.org
Subject: Source organization for two drivers sharing coomon code
Date: Fri, 27 Jul 2007 10:17:29 -0700	[thread overview]
Message-ID: <20070727171729.f3ff0878@mailhost.serverengines.com> (raw)



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.

Subbu

___________________________________________________________________________________
This message, together with any attachment(s), contains confidential and proprietary information of
ServerEngines LLC and is intended only for the designated recipient(s) named above. Any unauthorized
review, printing, retention, copying, disclosure or distribution is strictly prohibited.  If you are not the
intended recipient of this message, please immediately advise the sender by reply email message and
delete all copies of this message and any attachment(s). Thank you.


             reply	other threads:[~2007-07-27 17:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 17:17 Subbu Seetharaman [this message]
2007-07-27 17:35 ` Alan Cox
2007-07-27 19:03 ` Jan Engelhardt
2007-07-27 19:12   ` Chris Friesen
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=20070727171729.f3ff0878@mailhost.serverengines.com \
    --to=subbus@serverengines.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®