linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: linux-mips@vger.kernel.org, philmd@linaro.org
Subject: Re: [PATCH v2 0/2] MIPS Booting fixes
Date: Mon, 27 Feb 2023 23:54:08 +0100	[thread overview]
Message-ID: <20230227225408.GA23071@alpha.franken.de> (raw)
In-Reply-To: <20230227184614.70026-1-jiaxun.yang@flygoat.com>

On Mon, Feb 27, 2023 at 06:46:12PM +0000, Jiaxun Yang wrote:
> Hi all,
> 
> This patchset fixes two issues that was found when doing reboot
> stress test on Malta/Boston FPGA board with various MIPS cores.
> 
> Perhaps they should go through the mips-fixes tree.
> 
> Thanks
> 
> Jiaxun Yang (2):
>   MIPS: smp-cps: Don't rely on CP0_CMGCRBASE
>   MIPS: cevt-r4k: Offset the value used to clear compare interrupt
> 
>  arch/mips/include/asm/smp-cps.h |  4 ++++
>  arch/mips/kernel/cevt-r4k.c     |  4 ++--
>  arch/mips/kernel/cps-vec.S      | 35 ++++++++++++++-------------------
>  arch/mips/kernel/smp-cps.c      |  2 ++
>  4 files changed, 23 insertions(+), 22 deletions(-)
> 
> -- 
> 2.37.1 (Apple Git-137.1)

applied to mips-next (will send in a second PR for this merge window).

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2023-02-27 22:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 18:46 [PATCH v2 0/2] MIPS Booting fixes Jiaxun Yang
2023-02-27 18:46 ` [PATCH v2 1/2] MIPS: smp-cps: Don't rely on CP0_CMGCRBASE Jiaxun Yang
2023-02-27 18:46 ` [PATCH v2 2/2] MIPS: cevt-r4k: Offset the value used to clear compare interrupt Jiaxun Yang
2023-02-27 22:54 ` Thomas Bogendoerfer [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=20230227225408.GA23071@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=philmd@linaro.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).