From: Daniel Walker <dwalker@fifo99.com>
To: Gregory Haskins <gregory.haskins@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Tips for module_init() dependencies
Date: Thu, 15 Oct 2009 09:12:09 -0700 [thread overview]
Message-ID: <1255623129.22917.41.camel@desktop> (raw)
In-Reply-To: <4AD7469B.9070907@gmail.com>
On Thu, 2009-10-15 at 11:58 -0400, Gregory Haskins wrote:
> Hi Daniel,
>
> Possibly.
>
> A) Any suggestions on how? Can I express this in Kconfig or something
> (i.e. "depends on FOO"). I currently have "select FOO" in the BAR
> object, but this doesn't seem to be sufficient to describe the relationship.
>
> B) Do I have to make the entire chain follow suit? (I have C deps on B,
> B deps on A kind of scenarios)
Yeah, what Randy said .. As far as I know it should be just a build
order issue .. In the make file when you specify your new module along
with all the others where you put it is actually important .. In
fs/Makefile you have this line,
obj-$(CONFIG_CONFIGFS_FS) += configfs/
and I would guess you want yours after that line if your adding to that
makefile.
Daniel
next prev parent reply other threads:[~2009-10-15 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 13:01 Tips for module_init() dependencies Gregory Haskins
2009-10-15 15:45 ` Daniel Walker
2009-10-15 15:58 ` Gregory Haskins
2009-10-15 16:06 ` Randy Dunlap
2009-10-15 16:13 ` Gregory Haskins
2009-10-15 16:18 ` Randy Dunlap
2009-10-15 16:12 ` Daniel Walker [this message]
2009-10-15 16:17 ` Gregory Haskins
2009-10-15 16:21 ` Daniel Walker
2009-10-15 16:50 ` Gregory Haskins
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=1255623129.22917.41.camel@desktop \
--to=dwalker@fifo99.com \
--cc=gregory.haskins@gmail.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