From: Emil Renner Berthing <kernel@esmil.dk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@rivosinc.com>,
Jessica Clarke <jrtc27@jrtc27.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] RISC-V: Fix cpumask rework falloout
Date: Mon, 31 Jan 2022 18:52:43 +0100 [thread overview]
Message-ID: <CANBLGcyZ+wcBiZOyd8jC2-cUx_m+Zu6XZB6gyDOL_omQzEesPw@mail.gmail.com> (raw)
In-Reply-To: <cover.1643635156.git.geert@linux-m68k.org>
On Mon, 31 Jan 2022 at 14:26, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> Hi all,
>
> This patch series intends to fix the fall-out from commit
> 26fb751ca37846c9 ("RISC-V: Do not use cpumask data structure for hartid
> bitmap"), cfr. the discussion in thread[1].
>
> Thanks for your comments!
>
> [1] "[PATCH v3 6/6] RISC-V: Do not use cpumask data structure for hartid
> bitmap"
> https://lore.kernel.org/r/20220120090918.2646626-7-atishp@rivosinc.com/
>
> Geert Uytterhoeven (3):
> RISC-V: Fix hartid mask handling for hartid 31 and up
> RISC-V: Fix handling of empty cpu masks
> RISC-V: Fix IPI/RFENCE hmask on non-monotonic hartid ordering
>
> arch/riscv/kernel/sbi.c | 72 +++++++++++++++++++++++++++--------------
> 1 file changed, 47 insertions(+), 25 deletions(-)
I built this and rebooted my Starlight board a number of times without
seeing any of the errors that usually shows up when [1] is not
reverted.
Tested-by: Emil Renner Berthing <kernel@esmil.dk>
[1]: 26fb751ca37846c9 ("RISC-V: Do not use cpumask data structure for
hartid bitmap")
prev parent reply other threads:[~2022-01-31 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 13:26 [PATCH 0/3] RISC-V: Fix cpumask rework falloout Geert Uytterhoeven
2022-01-31 13:26 ` [PATCH 1/3] RISC-V: Fix hartid mask handling for hartid 31 and up Geert Uytterhoeven
2022-01-31 13:26 ` [PATCH 2/3] RISC-V: Fix handling of empty cpu masks Geert Uytterhoeven
2022-01-31 21:16 ` Atish Patra
2022-01-31 13:26 ` [PATCH 3/3] RISC-V: Fix IPI/RFENCE hmask on non-monotonic hartid ordering Geert Uytterhoeven
2022-01-31 21:18 ` Atish Patra
2022-01-31 17:52 ` Emil Renner Berthing [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=CANBLGcyZ+wcBiZOyd8jC2-cUx_m+Zu6XZB6gyDOL_omQzEesPw@mail.gmail.com \
--to=kernel@esmil.dk \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=geert@linux-m68k.org \
--cc=jrtc27@jrtc27.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).