From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] CONFIGFS_FS must depend on SYSFS
Date: Mon, 10 Apr 2006 20:35:22 +0200 [thread overview]
Message-ID: <20060410183522.GE2408@stusta.de> (raw)
In-Reply-To: <20060327030622.GV7844@ca-server1.us.oracle.com>
On Sun, Mar 26, 2006 at 07:06:22PM -0800, Joel Becker wrote:
> On Sun, Mar 26, 2006 at 02:25:52PM +0200, Adrian Bunk wrote:
> > This patch fixes the following compile error with CONFIG_SYSFS=n:
> >
> > <-- snip -->
> >
> > ...
> > LD .tmp_vmlinux1
> > fs/built-in.o: In function `configfs_init':mount.c:(.init.text+0x3d5d): undefined reference to `kernel_subsys'
> > make: *** [.tmp_vmlinux1] Error 1
>
> Hmm. We only rely on SYSFS because of the policy decree of
> default mounting at /sys/kernel/config (just like GregKH was asked to
> put debugfs at /sys/kernel/debug). While we create the mount point, we
> don't rely on it. You can mount configfs anywhere you like.
> So, what do you think of making that part of the code check for
> CONFIG_SYSFS? Then the module can be built without SYSFS instead of
> depending on it. I'm open to either idea. Certainly, we don't leave
> the compile error.
First of all sorry for the late answer.
My intention is to get the compile error fixed, and I don't care that
much how it gets fixed.
OTOH, there's the question whether it matters at all - is the
intersection of the people who are in such space-limited environments
that they are setting CONFIG_EMBEDDED=y and then CONFIG_SYSFS=n and
the people using OCFS2 actually non-empty?
> Joel
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-04-10 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 12:25 [2.6 patch] CONFIGFS_FS must depend on SYSFS Adrian Bunk
2006-03-27 3:06 ` Joel Becker
2006-04-10 18:35 ` Adrian Bunk [this message]
2006-04-10 18:46 ` Joel Becker
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=20060410183522.GE2408@stusta.de \
--to=bunk@stusta.de \
--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