All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Helge Hafting <helgehaf@aitel.hist.no>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.21-rc5-mm2 - compile error on x86-64
Date: Thu, 29 Mar 2007 15:23:17 -0700	[thread overview]
Message-ID: <20070329152317.56df80d0.akpm@linux-foundation.org> (raw)
In-Reply-To: <m1mz1vem51.fsf@ebiederm.dsl.xmission.com>

On Thu, 29 Mar 2007 16:10:50 -0600
ebiederm@xmission.com (Eric W. Biederman) wrote:

> Andrew Morton <akpm@linux-foundation.org> writes:
> >
> > Ah.  I assume you have CONFIG_SYSCTL=y, CONFIG_PROC_SYSCTL=n?
> >
> >
> >
> >
> > From: Andrew Morton <akpm@linux-foundation.org>
> >
> > We're using #ifdef CONFIG_SYSCTL, but we should be using CONFIG_PROC_SYSCTL,
> > so we get
> 
> I have no problem with the patch it is clearly more correct than what we
> are doing now but I didn't think it was possible to select
> CONFIG_SYSCTL and CONFIG_PROCFS without CONFIG_PROC_SYSCTL being
> selected...
> Do we have a constraint problem in Kconfig?  Or am I misremembering things?
> 

config PROC_SYSCTL
        bool "Sysctl support (/proc/sys)" if EMBEDDED
        depends on PROC_FS
        select SYSCTL
        default y

CONFIG_PROC_SYSCTL depends on CONFIG_PROC_FS
CONFIG_PROC_SYSCTL selects CONFIG_SYSCTL

So I don't see anything preventing CONFIG_SYSCTL=y, CONFIG_PROC_FS=y,
CONFIG_PROC_SYSCTL=n.  I assume we can make this combination compile, link
and run easily enough.  I dunno if it makes any actual sense though?


I'd have thought that PROC_SYSCTL should just depend on SYSCTL.  But
SYSCTL's Kconfig setup is weird.


  reply	other threads:[~2007-03-29 22:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27  5:16 2.6.21-rc5-mm2 Andrew Morton
2007-03-27 10:04 ` 2.6.21-rc5-mm2 William Lee Irwin III
2007-03-28 17:02 ` 2.6.21-rc5-mm2 Andreas Mohr
2007-03-28 17:33   ` 2.6.21-rc5-mm2 Andreas Mohr
2007-03-28 17:45     ` 2.6.21-rc5-mm2 Andreas Mohr
2007-03-28 18:04       ` tty OOPS (Re: 2.6.21-rc5-mm2) Andreas Mohr
2007-03-28 18:38         ` Alexey Dobriyan
2007-03-28 18:56           ` Alexey Dobriyan
2007-03-28 20:07             ` Andrew Morton
2007-03-29 12:48               ` Maneesh Soni
2007-03-28 20:15             ` [FIXED] " Andreas Mohr
2007-03-28 21:08               ` Ethan Solomita
2007-03-28 21:27               ` Ethan Solomita
2007-03-28 17:42 ` 2.6.21-rc5-mm2 Christian
2007-03-28 17:55   ` 2.6.21-rc5-mm2 Pallipadi, Venkatesh
2007-03-28 18:36 ` 2.6.21-rc5-mm2 Badari Pulavarty
2007-03-28 20:20 ` 2.6.21-rc5-mm2 OOPS and spinlock lockup Zan Lynx
2007-03-28 20:50   ` Andrew Morton
2007-03-29 17:53 ` 2.6.21-rc5-mm2 Badari Pulavarty
2007-03-29 17:23   ` 2.6.21-rc5-mm2 Andrew Morton
2007-03-29 18:20 ` 2.6.21-rc5-mm2 - compile error on x86-64 Helge Hafting
2007-03-29 21:28   ` Andrew Morton
2007-03-29 22:10     ` Eric W. Biederman
2007-03-29 22:23       ` Andrew Morton [this message]
2007-03-30  5:10         ` Eric W. Biederman
2007-03-29 22:24       ` Randy Dunlap
2007-03-31  6:27     ` Helge Hafting
2007-03-31  6:53       ` Eric W. Biederman
2007-03-31  6:50     ` Helge Hafting

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=20070329152317.56df80d0.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=helgehaf@aitel.hist.no \
    --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.