From: Joel Becker <Joel.Becker@oracle.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] CONFIGFS_FS must depend on SYSFS
Date: Mon, 10 Apr 2006 11:46:04 -0700 [thread overview]
Message-ID: <20060410184604.GZ29730@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20060410183522.GE2408@stusta.de>
On Mon, Apr 10, 2006 at 08:35:22PM +0200, Adrian Bunk wrote:
> 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?
We decided that (configfs + !sysfs == 0), and we just went with
the direct dependancy. It's in my tree, going to Linus whenever it gets
there.
Joel
--
"I don't even butter my bread; I consider that cooking."
- Katherine Cebrian
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
prev parent reply other threads:[~2006-04-10 18:49 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
2006-04-10 18:46 ` Joel Becker [this message]
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=20060410184604.GZ29730@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=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