From: Ralf Baechle <ralf@linux-mips.org>
To: Huacai Chen <chenhc@lemote.com>
Cc: John Crispin <john@phrozen.org>,
"Steven J. Hill" <Steven.Hill@imgtec.com>,
linux-mips@linux-mips.org, Fuxin Zhang <zhangfx@lemote.com>,
Zhangjin Wu <wuzhangjin@gmail.com>
Subject: Re: [PATCH V2 4/4] MIPS: Loongson: Make CPU names more clear
Date: Tue, 10 Nov 2015 12:12:54 +0100 [thread overview]
Message-ID: <20151110111253.GB29184@linux-mips.org> (raw)
In-Reply-To: <1444198082-24128-5-git-send-email-chenhc@lemote.com>
On Wed, Oct 07, 2015 at 02:08:02PM +0800, Huacai Chen wrote:
> Make names in /proc/cpuinfo more human-readable, Since GCC support the
> new-style names for a long time, this may not break -march=native any
> more.
I do understand why you want to make this change - but things in proc
including CPU names are interfaces and those are cast in stone. You
can't just call a potatoe a cherry today :-)
Unless you have a good reason which would include demonstrating that is
not breaking any existing application code?
Ralf
next prev parent reply other threads:[~2015-11-10 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 6:07 [PATCH V2 0/4] MIPS: Loongson-3: Improve kernel functionality Huacai Chen
2015-10-07 6:07 ` [PATCH V2 1/4] MIPS: Loongson: Cleanup CONFIG_LOONGSON_SUSPEND Huacai Chen
2015-10-07 6:08 ` [PATCH V2 2/4] MIPS: Loongson-3: Move chipset ACPI code from drivers to arch Huacai Chen
2015-11-12 3:55 ` Huacai Chen
2015-10-07 6:08 ` [PATCH V2 3/4] MIPS: Loongson: Introduce and use cpu_has_coherent_cache feature Huacai Chen
2015-11-12 3:55 ` Huacai Chen
2015-10-07 6:08 ` [PATCH V2 4/4] MIPS: Loongson: Make CPU names more clear Huacai Chen
2015-11-10 11:12 ` Ralf Baechle [this message]
2015-11-12 1:19 ` 陈华才
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=20151110111253.GB29184@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Steven.Hill@imgtec.com \
--cc=chenhc@lemote.com \
--cc=john@phrozen.org \
--cc=linux-mips@linux-mips.org \
--cc=wuzhangjin@gmail.com \
--cc=zhangfx@lemote.com \
/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