From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Suren Baghdasaryan <surenb@google.com>,
peterz@infradead.org, andrii@kernel.org, jannh@google.com,
Liam.Howlett@oracle.com, lorenzo.stoakes@oracle.com,
vbabka@suse.cz, mhocko@kernel.org, shakeel.butt@linux.dev,
hannes@cmpxchg.org, david@redhat.com, willy@infradead.org,
brauner@kernel.org, oleg@redhat.com, arnd@arndb.de,
richard.weiyang@gmail.com, zhangpeng.00@bytedance.com,
linmiaohe@huawei.com, viro@zeniv.linux.org.uk,
hca@linux.ibm.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: convert mm_lock_seq to a proper seqcount
Date: Tue, 29 Oct 2024 14:14:54 -0700 [thread overview]
Message-ID: <CAEf4BzZODA7AkC6Y7d_fhGnR3MH8MV-0QZC6aKi0FfwJwv++PQ@mail.gmail.com> (raw)
In-Reply-To: <20241028204822.6638f330fad809381eafb49c@linux-foundation.org>
On Mon, Oct 28, 2024 at 8:48 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Sun, 27 Oct 2024 17:57:34 -0700 Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
>
> > I got a notification that this patch set was applied to mm-unstable by
> > Andrew. But I was wondering if Andrew and Peter would agree to move
> > the patches into tip's perf/core branch, given this is a dependency of
> > my pending uprobe series ([0]) and, as far as I'm aware, there is no
> > urgent need for this API in mm tree(s).
>
> OK by me.
Great, thank you! Then I'll hope Peter will just apply all 4 patches
into his tree.
prev parent reply other threads:[~2024-10-29 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 20:52 Suren Baghdasaryan
2024-10-24 20:52 ` [PATCH 2/2] mm: introduce mmap_lock_speculation_{begin|end} Suren Baghdasaryan
2024-10-28 0:57 ` [PATCH 1/2] mm: convert mm_lock_seq to a proper seqcount Andrii Nakryiko
2024-10-28 1:24 ` Andrii Nakryiko
2024-10-29 3:48 ` Andrew Morton
2024-10-29 21:14 ` Andrii Nakryiko [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=CAEf4BzZODA7AkC6Y7d_fhGnR3MH8MV-0QZC6aKi0FfwJwv++PQ@mail.gmail.com \
--to=andrii.nakryiko@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hca@linux.ibm.com \
--cc=jannh@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=richard.weiyang@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=zhangpeng.00@bytedance.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