From: Greg KH <greg@kroah.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Adrian Bunk <bunk@stusta.de>,
Alessandro Suardi <alessandro.suardi@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-git2: CONFIGFS_FS shows up as M/y choice, help says "if unsure, say N"
Date: Mon, 9 Jan 2006 11:19:07 -0800 [thread overview]
Message-ID: <20060109191907.GA22881@kroah.com> (raw)
In-Reply-To: <20060109085430.GG18439@ca-server1.us.oracle.com>
On Mon, Jan 09, 2006 at 12:54:30AM -0800, Joel Becker wrote:
> On Sun, Jan 08, 2006 at 08:29:43PM +0100, Jan Engelhardt wrote:
> > Well ok. What I mean is: I don't want to have configfs if I do not also
> > want ocfs2.
>
> While I can see where you are coming from, there are other
> projects (not in-tree yet) that use configfs that may not use ocfs2.
> Red Hat's cluster stuff plays with it, I think CKRM has as well. They
> need the ability to select it without selecting ocfs2, and they are
> definitely not EMBEDDED.
> Is there any other way we can satisfy this?
I don't really think there's a problem.
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-09 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 21:10 2.6.15-git2: CONFIGFS_FS shows up as M/y choice, help says "if unsure, say N" Alessandro Suardi
2006-01-06 21:39 ` Lennart Sorensen
2006-01-06 21:46 ` Alessandro Suardi
2006-01-06 21:46 ` Kyle Moffett
2006-01-06 21:49 ` Alessandro Suardi
2006-01-06 22:30 ` Joel Becker
2006-01-07 22:09 ` Adrian Bunk
2006-01-08 2:16 ` Greg KH
2006-01-08 11:48 ` Jan Engelhardt
2006-01-08 16:27 ` Greg KH
2006-01-08 19:29 ` Jan Engelhardt
2006-01-09 8:54 ` Joel Becker
2006-01-09 19:19 ` Greg KH [this message]
2006-01-10 4:08 ` Adrian Bunk
2006-01-07 0:54 ` Dave Jones
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=20060109191907.GA22881@kroah.com \
--to=greg@kroah.com \
--cc=alessandro.suardi@gmail.com \
--cc=bunk@stusta.de \
--cc=jengelh@linux01.gwdg.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