linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: bcm2835: enable proc and sysfs in defconfig
Date: Sun, 28 Oct 2012 13:28:07 +0100	[thread overview]
Message-ID: <20121028132807.266a1d52@skate> (raw)
In-Reply-To: <508D1A65.20506@mvista.com>

Dear Sergei Shtylyov,

On Sun, 28 Oct 2012 15:43:33 +0400, Sergei Shtylyov wrote:

> > diff --git a/arch/arm/configs/bcm2835_defconfig b/arch/arm/configs/bcm2835_defconfig
> > index 7aea702..74e27f0 100644
> > --- a/arch/arm/configs/bcm2835_defconfig
> > +++ b/arch/arm/configs/bcm2835_defconfig
> > @@ -66,8 +66,6 @@ CONFIG_TTY_PRINTK=y
> >   # CONFIG_FILE_LOCKING is not set
> >   # CONFIG_DNOTIFY is not set
> >   # CONFIG_INOTIFY_USER is not set
> > -# CONFIG_PROC_FS is not set
> > -# CONFIG_SYSFS is not set
> 
>     Hm, I don't see where are you enabling them... So I miss something?

Yes:

config PROC_FS
        bool "/proc file system support" if EXPERT
        default y

config SYSFS
        bool "sysfs file system support" if EXPERT
        default y

Those options are enabled by default. So, when there's nothing in the
defconfig file to disable them, they are enabled.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-10-28 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-27 17:00 [PATCH] arm: bcm2835: enable proc and sysfs in defconfig Thomas Petazzoni
2012-10-28  2:33 ` Stephen Warren
2012-10-28 11:43 ` Sergei Shtylyov
2012-10-28 12:28   ` Thomas Petazzoni [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=20121028132807.266a1d52@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).