From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Greg KH <gregkh@suse.de>, Peter Jones <pjones@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Scott James Remnant <scott@canonical.com>,
Kay Sievers <kay.sievers@vrfy.org>, Dave Jones <davej@redhat.com>
Subject: Re: can we move USB_DEVICEFS to non-embedded?
Date: Thu, 9 Jul 2009 08:43:06 +0800 [thread overview]
Message-ID: <b6a2187b0907081743w61102ff4u75d15c2f3cae26d@mail.gmail.com> (raw)
In-Reply-To: <21d7e9970907081423v6d3830eey227f3d54b10382a6@mail.gmail.com>
On Thu, Jul 9, 2009 at 5:23 AM, Dave Airlie<airlied@gmail.com> wrote:
> So I don't think CONFIG_EMBEDDED is correct at least at this point.
Without CONFIG_EMBEDDED ...
CONFIG_NAMESPACES=y
With CONFIG_EMBEDDED=y ...
# CONFIG_NAMESPACES is not set
CONFIG_VMSPLIT_3G=y
I can't find a place to change these using menuconfig when EMBEDDED is selected.
I agree that CONFIG_EMBEDDED is not the right place to hide this
becuase it changed the behavior of more than just usbfs.
Thanks,
Jeff
next prev parent reply other threads:[~2009-07-09 0:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 5:11 Jeff Chua
2009-06-23 8:17 ` Scott James Remnant
2009-06-23 14:42 ` Greg KH
2009-06-23 15:29 ` Jeff Chua
2009-06-23 15:39 ` Greg KH
2009-07-08 10:54 ` Dave Airlie
2009-07-08 11:03 ` Kay Sievers
2009-07-08 11:20 ` Dave Airlie
2009-07-08 11:42 ` Scott James Remnant
2009-07-08 13:00 ` Greg KH
2009-07-08 13:52 ` Peter Jones
2009-07-08 13:55 ` Peter Jones
2009-07-08 14:04 ` Greg KH
2009-07-08 14:12 ` Peter Jones
2009-07-08 14:56 ` Greg KH
2009-07-08 15:05 ` Peter Jones
2009-07-08 15:47 ` Greg KH
2009-07-08 21:23 ` Dave Airlie
2009-07-09 0:43 ` Jeff Chua [this message]
2009-07-09 1:59 ` Randy Dunlap
2009-07-09 2:31 ` Jeff Chua
2009-07-09 3:01 ` Randy Dunlap
2009-07-09 12:12 ` Jeff Chua
2009-07-09 1:33 ` Greg KH
2009-07-08 15:12 ` Bill Nottingham
2009-07-08 15:44 ` Greg KH
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=b6a2187b0907081743w61102ff4u75d15c2f3cae26d@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=airlied@gmail.com \
--cc=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=scott@canonical.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®