From: Geert Uytterhoeven <geert@linux-m68k.org> To: 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> Cc: Jessica Clarke <jrtc27@jrtc27.com>, Emil Renner Berthing <kernel@esmil.dk>, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven <geert@linux-m68k.org> Subject: [PATCH 0/3] RISC-V: Fix cpumask rework falloout Date: Mon, 31 Jan 2022 14:26:19 +0100 [thread overview] Message-ID: <cover.1643635156.git.geert@linux-m68k.org> (raw) 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(-) -- 2.25.1 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org> To: 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> Cc: Jessica Clarke <jrtc27@jrtc27.com>, Emil Renner Berthing <kernel@esmil.dk>, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven <geert@linux-m68k.org> Subject: [PATCH 0/3] RISC-V: Fix cpumask rework falloout Date: Mon, 31 Jan 2022 14:26:19 +0100 [thread overview] Message-ID: <cover.1643635156.git.geert@linux-m68k.org> (raw) 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(-) -- 2.25.1 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-01-31 13:26 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-31 13:26 Geert Uytterhoeven [this message] 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 ` Geert Uytterhoeven 2022-01-31 13:26 ` [PATCH 2/3] RISC-V: Fix handling of empty cpu masks Geert Uytterhoeven 2022-01-31 13:26 ` Geert Uytterhoeven 2022-01-31 21:16 ` Atish Patra 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 13:26 ` Geert Uytterhoeven 2022-01-31 21:18 ` Atish Patra 2022-01-31 21:18 ` Atish Patra 2022-01-31 17:52 ` [PATCH 0/3] RISC-V: Fix cpumask rework falloout Emil Renner Berthing 2022-01-31 17:52 ` Emil Renner Berthing
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=cover.1643635156.git.geert@linux-m68k.org \ --to=geert@linux-m68k.org \ --cc=anup@brainfault.org \ --cc=aou@eecs.berkeley.edu \ --cc=atishp@rivosinc.com \ --cc=jrtc27@jrtc27.com \ --cc=kernel@esmil.dk \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.