From: Roland McGrath <roland@redhat.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-arch@vger.kernel.org, linuxppc-dev@ozlabs.org,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] compat_binfmt_elf Kconfig
Date: Wed, 2 Jan 2008 14:12:28 -0800 (PST) [thread overview]
Message-ID: <20080102221228.C9D8D26F9A0@magilla.localdomain> (raw)
In-Reply-To: Sam Ravnborg's message of Wednesday, 2 January 2008 22:53:11 +0100 <20080102215311.GA12558@uranus.ravnborg.org>
I have no opinions about the config symbol names. Among the existing
precedents for internal/descriptionless symbols I find more not using the
HAVE_ prefix than those using it. The patch versions I've sent now work
fine, fix the parallel build problem people were seeing, and AFAICT follow
the style of what's already in common use. At this point, I think it would
be easiest just to keep them and have you send symbol-renaming patches
for any and all symbols of this sort that concern you as separate cleanups.
Thanks,
Roland
next prev parent reply other threads:[~2008-01-02 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071223183920.GA13976@elte.hu>
[not found] ` <20071223211603.3FFB126F8E7@magilla.localdomain>
[not found] ` <20071230163614.GB1384@elte.hu>
[not found] ` <20080102044157.A5CC526F99F@magilla.localdomain>
[not found] ` <20080102111431.GD14731@elte.hu>
[not found] ` <20080102191030.GA11217@uranus.ravnborg.org>
2008-01-02 21:08 ` [PATCH -mm] compat_binfmt_elf Kconfig Roland McGrath
2008-01-02 21:12 ` [PATCH -mm] x86 compat_binfmt_elf, " Roland McGrath
2008-01-02 21:58 ` [PATCH -mm] x86 compat_binfmt_elf Ingo Molnar
2008-01-02 21:17 ` [PATCH -mm] powerpc compat_binfmt_elf Roland McGrath
2008-01-02 21:53 ` [PATCH -mm] compat_binfmt_elf Kconfig Sam Ravnborg
2008-01-02 21:59 ` Sam Ravnborg
2008-01-02 22:12 ` Roland McGrath [this message]
2008-01-03 7:23 ` Sam Ravnborg
2008-01-02 21:57 ` Ingo Molnar
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=20080102221228.C9D8D26F9A0@magilla.localdomain \
--to=roland@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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