From: Peng Zhang <zhangpeng.00@bytedance.com>
To: Marco Elver <elver@google.com>
Cc: glider@google.com, dvyukov@google.com, akpm@linux-foundation.org,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, muchun.song@linux.dev,
Peng Zhang <zhangpeng.00@bytedance.com>
Subject: Re: [PATCH v2] mm: kfence: allocate kfence_metadata at runtime
Date: Tue, 18 Jul 2023 15:35:01 +0800 [thread overview]
Message-ID: <f0aa25be-8f44-b71c-baf9-f22890c32329@bytedance.com> (raw)
In-Reply-To: <CANpmjNOhNQuBZAgOKLv4+4UoFK1b_8PP0EzWzkuyyGE0bg+weg@mail.gmail.com>
Thank you for your review, I have updated v3[1] with all
the changes you mentioned.
[1]
https://lore.kernel.org/lkml/20230718073019.52513-1-zhangpeng.00@bytedance.com/
Thanks,
Peng
prev parent reply other threads:[~2023-07-18 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 8:16 Peng Zhang
2023-07-12 9:30 ` Alexander Potapenko
2023-07-12 9:36 ` Peng Zhang
2023-07-14 12:42 ` Peng Zhang
2023-07-17 10:07 ` Marco Elver
2023-07-18 7:35 ` Peng Zhang [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=f0aa25be-8f44-b71c-baf9-f22890c32329@bytedance.com \
--to=zhangpeng.00@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
/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