From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Building two (external) modules from the same sources
Date: Mon, 29 Sep 2008 09:49:34 +0400 [thread overview]
Message-ID: <200809290949.35749.arvidjaar@mail.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
I have here driver that can be built for two different types of
hardware from basically the same sources (this is port of old Agere
drivers for Hermes-I/Hermes-II chipsets). Build differs only in one
define -DHERMES2 and single file with different firmware. Unfortunately
"if HII" are spread over sources which makes splitting of sources rather
questionable.
What is the best way (from kbuild POV) to build two modules - for H-I
and H-II - from the same set of source files?
TIA
-andrey
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-09-29 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 5:49 Andrey Borzenkov [this message]
2008-10-01 3:19 ` Building two (external) modules from the same sources Greg KH
2008-10-01 10:13 ` Andrey Borzenkov
2008-10-01 20:05 ` Greg KH
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=200809290949.35749.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-kbuild@vger.kernel.org \
--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