From: Sam Ravnborg <sam@ravnborg.org>
To: Hirokazu Takata <takata@linux-m32r.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.10-rc1-bk21] [m32r] Update defconfig files
Date: Sat, 13 Nov 2004 23:09:18 +0100 [thread overview]
Message-ID: <20041113220918.GD8319@mars.ravnborg.org> (raw)
In-Reply-To: <20041112.173414.28782636.takata.hirokazu@renesas.com>
On Fri, Nov 12, 2004 at 05:34:14PM +0900, Hirokazu Takata wrote:
> Hello,
>
> This patch is for updating defconfig files for m32r.
> All defconfig files are regenerated for 2.6.10-rc1-bk21.
>
> Thanks.
>
> Signed-off-by: Hirokazu Takata <takata@linux-m32r.org>
> ---
>
> arch/m32r/defconfig | 152 +++++-
> arch/m32r/m32700ut/defconfig.m32700ut.smp | 130 ++++-
> arch/m32r/m32700ut/defconfig.m32700ut.up | 130 ++++-
> arch/m32r/mappi/defconfig.nommu | 109 +++-
> arch/m32r/mappi/defconfig.smp | 104 +++-
> arch/m32r/mappi/defconfig.up | 104 +++-
> arch/m32r/mappi2/defconfig.vdec2 | 698 ++++++++++++++++++++++++++++++
> arch/m32r/oaks32r/defconfig.nommu | 93 +++
> arch/m32r/opsput/defconfig.opsput | 114 +++-
> 9 files changed, 1424 insertions(+), 210 deletions(-)
Any reason why you do not place them in arch/m32r/configs like ppc and arm?
If you name them like arm/ppc then you play like the rest of the archs.
As an added bonus the config options shows up in "make help".
You should also consider using the newly introduced KBUILD_DEFCONFIG.
Let it point to the most 'popular' of the arch/m32r/configs/defconfig* files
then you do not need the file arch/m32r/defconfig.
Sam
next prev parent reply other threads:[~2004-11-13 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 8:34 Hirokazu Takata
2004-11-13 22:09 ` Sam Ravnborg [this message]
2004-11-17 8:01 ` Hirokazu Takata
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=20041113220918.GD8319@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=takata@linux-m32r.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
all inboxes | Powered by JetHome®