From: Andrey Konovalov <andreyknvl@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: andrey.konovalov@linux.dev, Marco Elver <elver@google.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
kasan-dev@googlegroups.com,
Evgenii Stepanov <eugenis@google.com>,
Oscar Salvador <osalvador@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrey Konovalov <andreyknvl@google.com>
Subject: Re: [PATCH] fix for "lib/stackdepot: allow users to evict stack traces"
Date: Fri, 27 Oct 2023 01:20:39 +0200 [thread overview]
Message-ID: <CA+fCnZcy5cCHTtXmVmUngL_PPjLLX-O2uDYtSaM-=G_kO=GHMw@mail.gmail.com> (raw)
In-Reply-To: <20231026160715.ea74f79dea9960b8ff46d077@linux-foundation.org>
On Fri, Oct 27, 2023 at 1:07 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Fri, 27 Oct 2023 00:33:40 +0200 andrey.konovalov@linux.dev wrote:
>
> > From: Andrey Konovalov <andreyknvl@google.com>
> >
> > Commit "lib/stackdepot: allow users to evict stack traces" adds another
> > user for depot_fetch_stack, which holds a write lock. Thus, we need to
> > update the lockdep annotation.
> >
>
> We're at -rc7, which is rather late to be merging material such as this
> patchset. Please resend it all after -rc1 and include this fixup,
> thanks.
Ack.
I might send a few more additions to the series for review before
then, but then resend everything together after rc1.
prev parent reply other threads:[~2023-10-26 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 22:33 andrey.konovalov
2023-10-26 23:07 ` Andrew Morton
2023-10-26 23:20 ` Andrey Konovalov [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='CA+fCnZcy5cCHTtXmVmUngL_PPjLLX-O2uDYtSaM-=G_kO=GHMw@mail.gmail.com' \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrey.konovalov@linux.dev \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
/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