From: Paul Burton <paul.burton@mips.com>
To: Paul Burton <pburton@wavecomp.com>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
Paul Burton <pburton@wavecomp.com>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH 1/2] MIPS: r4k-bugs64: Limit R4k bug checks to affected systems
Date: Mon, 7 Oct 2019 17:53:16 +0000 [thread overview]
Message-ID: <MWHPR2201MB12770C80CCD2C6788101384EC19B0@MWHPR2201MB1277.namprd22.prod.outlook.com> (raw)
In-Reply-To: <20191001230423.70119-1-paul.burton@mips.com>
Hello,
Paul Burton wrote:
> Only build the checks for R4k errata workarounds if we expect that the
> kernel might actually run on a system with an R4k CPU - ie.
> CONFIG_SYS_HAS_CPU_R4X00=y & we're targeting a pre-MIPSr1 ISA revision.
>
> Rename cpu-bugs64.c to r4k-bugs64.c to indicate the fact that the code
> is specific to R4k CPUs.
Series applied to mips-next.
> MIPS: r4k-bugs64: Limit R4k bug checks to affected systems
> commit 071d2f0b5419
> https://git.kernel.org/mips/c/071d2f0b5419
>
> Signed-off-by: Paul Burton <paul.burton@mips.com>
>
> MIPS: r4k-bugs64: Drop CONFIG_CPU_MIPSR6 checks
> commit 5045d06b3736
> https://git.kernel.org/mips/c/5045d06b3736
>
> Signed-off-by: Paul Burton <paul.burton@mips.com>
Thanks,
Paul
[ This message was auto-generated; if you believe anything is incorrect
then please email paul.burton@mips.com to report it. ]
prev parent reply other threads:[~2019-10-07 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 23:04 [PATCH 1/2] MIPS: r4k-bugs64: Limit R4k bug checks to affected systems Paul Burton
2019-10-01 23:04 ` [PATCH 2/2] MIPS: r4k-bugs64: Drop CONFIG_CPU_MIPSR6 checks Paul Burton
2019-10-07 17:53 ` Paul Burton [this message]
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=MWHPR2201MB12770C80CCD2C6788101384EC19B0@MWHPR2201MB1277.namprd22.prod.outlook.com \
--to=paul.burton@mips.com \
--cc=linux-mips@vger.kernel.org \
--cc=pburton@wavecomp.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;
as well as URLs for NNTP newsgroup(s).