From: Martin Michlmayr <tbm@cyrius.com>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH 1/12] [MIPS] Improve description of VR41xx based machines
Date: Mon, 20 Mar 2006 13:10:53 +0000 [thread overview]
Message-ID: <20060320131053.GA29434@deprecation.cyrius.com> (raw)
In-Reply-To: <20060320152646.1c5690e3.yoichi_yuasa@tripeaks.co.jp>
* Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp> [2006-03-20 15:26]:
> > MIPS supports various NEC VR41XX chips and not just the VR4100.
> > Update Kconfig accordingly, thereby bringing the file in sync with
> > the linux-mips tree.
> The linux-mips tree is older than kernel.org about this part.
Have you looked at the exact change I sent (I know that linux-mips has
some older stuff, but the patch I sent was against linux-mips+new).
IOW, is it more correct to say "VR4100" in Kconfig rather than
"VR41XX", even though more CPUs than the VR4100 are supported?
All my patch does is a a/VR4100/VR41XX/, really.
> > - bool "Support for NEC VR4100 series based machines"
> > + bool "Support for NEC VR41XX-based machines"
...
> > - The options selects support for the NEC VR4100 series of processors.
> > + The options selects support for the NEC VR41xx series of processors.
> > Only choose this option if you have one of these processors as a
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2006-03-20 13:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 4:38 Bring mainline in sync with the linux-mips tree Martin Michlmayr
2006-03-20 4:39 ` [PATCH 1/12] [MIPS] Improve description of VR41xx based machines Martin Michlmayr
2006-03-20 6:26 ` Yoichi Yuasa
2006-03-20 13:10 ` Martin Michlmayr [this message]
2006-03-20 15:59 ` Yoichi Yuasa
2006-03-20 16:29 ` Martin Michlmayr
2006-03-21 2:10 ` Yoichi Yuasa
2006-03-21 2:18 ` Martin Michlmayr
2006-03-22 7:53 ` Yoichi Yuasa
2006-03-22 10:07 ` Martin Michlmayr
2006-03-20 4:39 ` [PATCH 2/12] [MIPS] Cosmetic updates to sync with linux-mips Martin Michlmayr
2006-03-20 6:31 ` Yoichi Yuasa
2006-03-20 13:11 ` Martin Michlmayr
2006-03-21 2:12 ` Yoichi Yuasa
2006-03-20 4:39 ` [PATCH 3/12] [MIPS] Remove tb0287_defconfig Martin Michlmayr
2006-03-20 6:23 ` Yoichi Yuasa
2006-03-20 4:39 ` [PATCH 4/12] [NET] Improve description of MV643XX_ETH Martin Michlmayr
2006-03-20 4:39 ` [PATCH 5/12] [NET] Bring declance.c in sync with linux-mips tree Martin Michlmayr
2006-03-20 4:40 ` [PATCH 6/12] [NET] Support the BCM1x55 and BCM1x80 chips Martin Michlmayr
2006-03-20 4:40 ` [PATCH 7/12] [IDE] Set CFLAGS only for au1xxx-ide Martin Michlmayr
2006-03-20 4:40 ` [PATCH 8/12] [MTD] Re-add module description for ms02-nv to Kconfig Martin Michlmayr
2006-03-20 4:40 ` [PATCH 9/12] [MTD] Fix #else directive in the docprobe driver Martin Michlmayr
2006-03-20 4:40 ` [PATCH 10/12] [MTD] LASAT depends on MTD_CFI Martin Michlmayr
2006-03-20 4:41 ` [PATCH 11/12] [USB] Cosmetic changes to bring ohci-au1xxx.c in sync with linux-mips Martin Michlmayr
2006-03-20 4:41 ` [PATCH 12/12] [SCSI] mem_start is a physical address already Martin Michlmayr
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=20060320131053.GA29434@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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