From: Christoph Hellwig <hch@infradead.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Andi Kleen <ak@novell.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] Deprecate a.out ELF interpreters
Date: Wed, 1 Aug 2007 21:02:33 +0100 [thread overview]
Message-ID: <20070801200233.GA30240@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0708012125290.26668@fbirervta.pbzchgretzou.qr>
On Wed, Aug 01, 2007 at 09:26:10PM +0200, Jan Engelhardt wrote:
>
> On Aug 1 2007 20:35, Andi Kleen wrote:
> >> On Aug 1 2007 14:33, Andi Kleen wrote:
> >> >Comments?
> >>
> >> A kconfig entry "(OBSOLETE)"/"(DEPRECATED)" would be nice.
> >> (And if you want to test people, 'depends on EMBEDDED' for CONFIG_BINFMT_AOUT)
> >
> >The point is to have less clutter in binfmt_elf.c (which really
> >could need a rewrite btw or at least a lot of cleanup) not add more in form
> >of ifdefs.
>
>
> ---
> fs/Kconfig.binfmt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6.23/fs/Kconfig.binfmt
> ===================================================================
> --- linux-2.6.23.orig/fs/Kconfig.binfmt
> +++ linux-2.6.23/fs/Kconfig.binfmt
> @@ -56,7 +56,7 @@ config BINFMT_SHARED_FLAT
> Support FLAT shared libraries
>
> config BINFMT_AOUT
> - tristate "Kernel support for a.out and ECOFF binaries"
> + tristate "Kernel support for a.out and ECOFF binaries (OBSOLETE)"
NAK, binfmt a.out support is something entirely different from what
we're talking about here.
next prev parent reply other threads:[~2007-08-01 20:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 12:33 [RFC] [PATCH] Deprecate a.out ELF interpreters Andi Kleen
2007-08-01 15:02 ` H. Peter Anvin
2007-08-01 18:30 ` Jan Engelhardt
2007-08-01 18:35 ` Andi Kleen
2007-08-01 19:26 ` Jan Engelhardt
2007-08-01 20:02 ` Christoph Hellwig [this message]
2007-08-01 20:13 ` Andi Kleen
2007-08-01 20:42 ` Jiri Kosina
2007-08-01 21:18 ` Rene Herman
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=20070801200233.GA30240@infradead.org \
--to=hch@infradead.org \
--cc=ak@novell.com \
--cc=jengelh@computergmbh.de \
--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