All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: 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: Sun, 8 Jan 2006 08:27:43 -0800	[thread overview]
Message-ID: <20060108162743.GA27234@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0601081247150.30148@yvahk01.tjqt.qr>

On Sun, Jan 08, 2006 at 12:48:03PM +0100, Jan Engelhardt wrote:
> >> Why is CONFIGFS_FS a user-visible option?
> >
> >I think it should be the same as SYSFS, only changable from the EMBEDDED
> >portion.
> >
> At its present state, no distribution uses configfs afaik, so I'd love to 
> have that turned off to not enlarge the kernel binary unnecessary.

Well, ocfs2 needs it, and as that just hit mainline, it's a bit unfair
to state that no distro uses it (and I think that it's even untrue, look
for the distros that ship ocfs2...)

thanks,

greg k-h

  reply	other threads:[~2006-01-08 16:41 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 [this message]
2006-01-08 19:29           ` Jan Engelhardt
2006-01-09  8:54             ` Joel Becker
2006-01-09 19:19               ` Greg KH
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=20060108162743.GA27234@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.