[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251008125639.GK3289052@noisy.programming.kicks-ass.net>
Date: Wed, 8 Oct 2025 14:56:39 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
Boqun Feng <boqun.feng@...il.com>,
David Howells <dhowells@...hat.com>, Ingo Molnar <mingo@...hat.com>,
Li RongQing <lirongqing@...du.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Waiman Long <longman@...hat.com>, Will Deacon <will@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/4] seqlock: introduce scoped_seqlock_read() and
scoped_seqlock_read_irqsave()
On Wed, Oct 08, 2025 at 02:30:14PM +0200, Oleg Nesterov wrote:
> Only 1/4 was changed according to comments from Linus and Waiman,
> but let me resend 2-4 as well.
Shall I put this in tip/locking/core once -rc1 happens or so?
Powered by blists - more mailing lists