All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Tigran Aivazian <tigran@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch-2.6.x] fix compile failure if CONFIG_PROC_KCORE not set.
Date: Fri, 3 Dec 2004 17:08:53 +0000	[thread overview]
Message-ID: <20041203170853.B24118@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0412031632310.4221@ezer.homenet>; from tigran@veritas.com on Fri, Dec 03, 2004 at 05:01:57PM +0000

On Fri, Dec 03, 2004 at 05:01:57PM +0000, Tigran Aivazian wrote:
> I know that /proc/kcore support cannot be disabled by normal means but 
> since it is conditional upon CONFIG_PROC_KCORE in fs/proc/Makefile it 
> makes sense to make sure that kernel compiles even if it is disabled 
> manually by editing .config and include/linux/autoconf.h or if in the 
> future CONFIG_PROC_KCORE becomes a real CONFIG_ variable.

CONFIG_PROC_KCORE currently exists to allow ARM and others to drop
the nonfunctional /proc/kcore support from the kernel.  It wasn't
intended to be a configuration option as such.

However, if you wish it to be so, there's no problem provided that
the architectures are fixed up as you've done for x86, and that the
ability for certain architectures to ensure that this is never
selected is preserved.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

      reply	other threads:[~2004-12-03 17:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 17:01 [patch-2.6.x] fix compile failure if CONFIG_PROC_KCORE not set Tigran Aivazian
2004-12-03 17:08 ` Russell King [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=20041203170853.B24118@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tigran@veritas.com \
    /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.