From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, willy@infradead.org, vbabka@suse.cz,
souravpanda@google.com, shakeel.butt@linux.dev,
richard.weiyang@gmail.com, peterx@redhat.com, paulmck@kernel.org,
pasha.tatashin@soleen.com, oleg@redhat.com, mjguzik@gmail.com,
minchan@google.com, mhocko@suse.com, mgorman@techsingularity.net,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
jannh@google.com, hughd@google.com, hdanton@sina.com,
hannes@cmpxchg.org, dhowells@redhat.com, david@redhat.com,
dave@stgolabs.net, corbet@lwn.net, brauner@kernel.org,
surenb@google.com
Subject: Re: + mm-convert-mm_lock_seq-to-a-proper-seqcount.patch added to mm-unstable branch
Date: Mon, 9 Dec 2024 09:42:03 +0100 [thread overview]
Message-ID: <20241209084203.GE21636@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241207042919.E4C44C4CECD@smtp.kernel.org>
On Fri, Dec 06, 2024 at 08:29:19PM -0800, Andrew Morton wrote:
>
> The patch titled
> Subject: mm: convert mm_lock_seq to a proper seqcount
> has been added to the -mm mm-unstable branch. Its filename is
> mm-convert-mm_lock_seq-to-a-proper-seqcount.patch
I'm having a pile of these patches in tip/perf/core
next prev parent reply other threads:[~2024-12-09 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 4:29 + mm-convert-mm_lock_seq-to-a-proper-seqcount.patch added to mm-unstable branch Andrew Morton
2024-12-09 8:42 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-25 22:58 Andrew Morton
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=20241209084203.GE21636@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hdanton@sina.com \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=minchan@google.com \
--cc=mjguzik@gmail.com \
--cc=mm-commits@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=paulmck@kernel.org \
--cc=peterx@redhat.com \
--cc=richard.weiyang@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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 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.