From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>
Cc: cijoml@volny.cz, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] kill CONFIG_KCORE_AOUT
Date: Sat, 30 Aug 2003 09:20:59 +0200 [thread overview]
Message-ID: <20030830072058.GI7038@fs.tum.de> (raw)
In-Reply-To: <20030830001159.013cc6d2.akpm@osdl.org>
On Sat, Aug 30, 2003 at 12:11:59AM -0700, Andrew Morton wrote:
> Adrian Bunk <bunk@fs.tum.de> wrote:
> >
> > The patch below kills CONFIG_KCORE_AOUT.
> >
> > I've tested the compilation with 2.6.0-test4.
>
> Not on m68knommu or h8300 you haven't :) They both
> select CONFIG_KCORE_AOUT in defconfig.
The Kconfig files on these architectures had the interesting "feature"
that both KCORE_AOUT and KCORE_ELF were enabled unconditionally...
Besides, I always consider the defconfig files as some kinds of
generated files and since they only give default answers for
"make defconfig" I didn't see the big need for manually editing every
single defconfig file.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-08-30 7:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 21:32 Can't compile 2.6.0-test4 Michal Semler (volny.cz)
2003-08-26 10:51 ` 2.6.0-test4: CONFIG_KCORE_AOUT doesn't compile Adrian Bunk
2003-08-26 12:28 ` Michal Semler (volny.cz)
2003-08-26 12:33 ` Adrian Bunk
2003-08-26 15:48 ` 2.6.0-test4 and /etc/modules.conf Michal Semler (volny.cz)
2003-08-26 16:00 ` Bas Mevissen
2003-08-26 16:37 ` Michal Semler (volny.cz)
2003-08-26 17:38 ` Emmanuele Bassi
2003-08-26 19:16 ` Felipe Alfaro Solana
2003-08-26 20:53 ` 2.6.0-test4: CONFIG_KCORE_AOUT doesn't compile Andrew Morton
2003-08-30 7:05 ` [2.6 patch] kill CONFIG_KCORE_AOUT Adrian Bunk
2003-08-30 7:11 ` Andrew Morton
2003-08-30 7:20 ` Adrian Bunk [this message]
2003-08-30 7:29 ` Andrew Morton
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=20030830072058.GI7038@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=cijoml@volny.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox