public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Charlie Jenkins <charlie@rivosinc.com>,
	Alexandre Ghiti <alexghiti@rivosinc.com>,
	Samuel Holland <samuel.holland@sifive.com>,
	Anup Patel <anup@brainfault.org>
Subject: Re: [PATCH 0/4] cleanup dead code in nodemasks and cpumasks
Date: Mon, 24 Mar 2025 11:02:24 -0400	[thread overview]
Message-ID: <Z-F0APn3eisfC0lC@thinkpad> (raw)
In-Reply-To: <20250313021953.86035-1-yury.norov@gmail.com>

Ping?

If no objections, I'll schedule it for 6.15.

On Wed, Mar 12, 2025 at 10:19:48PM -0400, Yury Norov wrote:
> Cleanup dead code in nodemasks and cpumasks, and while there, fix
> set_icache_stale_mask() that misuses atomic cpumask_assign_cpu().
> 
> Yury Norov (4):
>   nodemask: drop nodes_shift
>   cpumask: add non-atomic __assign_cpu()
>   riscv: switch set_icache_stale_mask() to using non-atomic assign_cpu()
>   cpumask: drop cpumask_assign_cpu()
> 
>  arch/riscv/mm/cacheflush.c |  2 +-
>  include/linux/cpumask.h    | 19 +++----------------
>  include/linux/nodemask.h   | 19 -------------------
>  3 files changed, 4 insertions(+), 36 deletions(-)
> 
> -- 
> 2.43.0

      parent reply	other threads:[~2025-03-24 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13  2:19 [PATCH 0/4] cleanup dead code in nodemasks and cpumasks Yury Norov
2025-03-13  2:19 ` [PATCH 1/4] nodemask: drop nodes_shift Yury Norov
2025-03-13  2:19 ` [PATCH 2/4] cpumask: add non-atomic __assign_cpu() Yury Norov
2025-03-13  2:19 ` [PATCH 3/4] riscv: switch set_icache_stale_mask() to using non-atomic assign_cpu() Yury Norov
2025-03-13  2:19 ` [PATCH 4/4] cpumask: drop cpumask_assign_cpu() Yury Norov
2025-03-24 15:02 ` Yury Norov [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=Z-F0APn3eisfC0lC@thinkpad \
    --to=yury.norov@gmail.com \
    --cc=alexghiti@rivosinc.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel.holland@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