From: Andrew Morton <akpm@linux-foundation.org>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: 1vier1@web.de, arnd@arndb.de, cgel.zte@gmail.com,
chi.minghao@zte.com.cn, dbueso@suse.de, mhocko@kernel.org,
mm-commits@vger.kernel.org, rdunlap@infradead.org,
shakeelb@google.com, stable@vger.kernel.org,
unixbhaskar@gmail.com, urezki@gmail.com, vvs@virtuozzo.com,
zealci@zte.com.cn
Subject: Re: + mm-utilc-make-kvfree-safe-for-calling-while-holding-spinlocks.patch added to -mm tree
Date: Thu, 27 Jan 2022 14:04:51 -0800 [thread overview]
Message-ID: <20220127140451.f6590de4579cefdf75dfd329@linux-foundation.org> (raw)
In-Reply-To: <5ae2873f-527f-9769-a606-4ff6786c0fcc@colorfullife.com>
On Thu, 27 Jan 2022 16:45:58 +0100 Manfred Spraul <manfred@colorfullife.com> wrote:
> Hi Andrew,
>
> On 1/27/22 03:55, akpm@linux-foundation.org wrote:
> > The patch titled
> > Subject: mm/util.c: make kvfree() safe for calling while holding spinlocks
> > has been added to the -mm tree. Its filename is
> > mm-utilc-make-kvfree-safe-for-calling-while-holding-spinlocks.patch
> >
> > This patch should soon appear at
> > https://ozlabs.org/~akpm/mmots/broken-out/mm-utilc-make-kvfree-safe-for-calling-while-holding-spinlocks.patch
> > and later at
> > https://ozlabs.org/~akpm/mmotm/broken-out/mm-utilc-make-kvfree-safe-for-calling-while-holding-spinlocks.patch
>
> Please drop and replace with
>
> https://marc.info/?l=linux-kernel&m=164132744522325&w=2
>
Ah, OK, that's been in -mm and -next for a month. I didn't send it
upstream because it wasn't clear to me which way we're going. I'll add
cc:stable and send it to Linus this week or next.
prev parent reply other threads:[~2022-01-27 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 2:55 + mm-utilc-make-kvfree-safe-for-calling-while-holding-spinlocks.patch added to -mm tree akpm
2022-01-27 15:45 ` Manfred Spraul
2022-01-27 22:04 ` Andrew Morton [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=20220127140451.f6590de4579cefdf75dfd329@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=1vier1@web.de \
--cc=arnd@arndb.de \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=dbueso@suse.de \
--cc=manfred@colorfullife.com \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=shakeelb@google.com \
--cc=stable@vger.kernel.org \
--cc=unixbhaskar@gmail.com \
--cc=urezki@gmail.com \
--cc=vvs@virtuozzo.com \
--cc=zealci@zte.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).