From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
"Maciej W . Rozycki" <macro@orcam.me.uk>,
Ralf Baechle <ralf@linux-mips.org>,
George Cherian <gcherian@marvell.com>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH v2] MIPS: select CPU_MIPS64 for remaining MIPS64 CPUs
Date: Mon, 1 Mar 2021 15:49:46 +0100 [thread overview]
Message-ID: <20210301144946.GD11261@alpha.franken.de> (raw)
In-Reply-To: <20210227230236.3234498-1-Jason@zx2c4.com>
On Sun, Feb 28, 2021 at 12:02:36AM +0100, Jason A. Donenfeld wrote:
> CPU_MIPS64 is supposed to be selected for CPUs that implement a revision
> of the MIPS64 ISA. While it contains the generic ones, it forgot about
> Octeon and Loongson in its list, which are indeed MIPS64 processors.
> This commit adds these missing CPUs to the auto-selection list.
>
> Cc: Maciej W. Rozycki <macro@orcam.me.uk>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: George Cherian <gcherian@marvell.com>
> Cc: Huacai Chen <chenhuacai@kernel.org>
> Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> arch/mips/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2021-03-01 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 12:26 [PATCH] MIPS: select CPU_MIPS64 for remaining MIPS64 CPUs Jason A. Donenfeld
2021-02-27 13:40 ` Maciej W. Rozycki
2021-02-27 22:59 ` Jason A. Donenfeld
2021-02-27 23:02 ` [PATCH v2] " Jason A. Donenfeld
2021-03-01 14:49 ` Thomas Bogendoerfer [this message]
2021-03-01 16:27 ` Jason A. Donenfeld
2021-03-02 23:03 ` Thomas Bogendoerfer
2021-03-03 0:05 ` Jason A. Donenfeld
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=20210301144946.GD11261@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Jason@zx2c4.com \
--cc=chenhuacai@kernel.org \
--cc=gcherian@marvell.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).