From: wang lian <lianux.mm@gmail.com>
To: lorenzo.stoakes@oracle.com
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
brauner@kernel.org, broonie@kernel.org,
david.laight.linux@gmail.com, david@redhat.com,
gkwang@linx-info.com, jannh@google.com, lianux.mm@gmail.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
ludovico.zy.wu@gmail.com, p1ucky0923@gmail.com, ryncsn@gmail.com,
shuah@kernel.org, sj@kernel.org, vbabka@suse.cz,
zijing.zhang@proton.me, ziy@nvidia.com
Subject: Re: [PATCH] selftests/mm: reuse FORCE_READ to replace "asm volatile("" : "+r" (XXX));"
Date: Sun, 20 Jul 2025 19:03:37 +0800 [thread overview]
Message-ID: <20250720110337.55384-1-lianux.mm@gmail.com> (raw)
In-Reply-To: <f0503a61-f605-468e-ae15-c4934faea632@lucifer.local>
> Wang - do not do anything like this, please!
> Let's all have some empathy for this being one of Wang's first patches. I
> appreciate this patch and it's a strict improvement on the past situation
> AFAIC.
> Cheers, Lorenzo
Hi Lorenzo,
Thank you so much for your kind words and support. I truly appreciate
you stepping in to provide clarity and encouragement.
This discussion has been a great learning experience. It's support like yours
that makes me feel so welcome and passionate about contributing to the kernel.
Please rest assured, I will follow the correct guidance. I am working on the
updated process_madv patch now.
Thank you again for everything.
Best regards,
Wang Lian
prev parent reply other threads:[~2025-07-20 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 12:31 [PATCH] selftests/mm: reuse FORCE_READ to replace "asm volatile("" : "+r" (XXX));" wang lian
2025-07-16 13:16 ` David Hildenbrand
2025-07-16 22:15 ` Andrew Morton
2025-07-17 6:58 ` Wei Yang
2025-07-17 10:48 ` wang lian
2025-07-17 11:43 ` David Hildenbrand
2025-07-19 9:27 ` David Laight
2025-07-20 9:23 ` Lorenzo Stoakes
2025-07-20 11:03 ` wang lian [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=20250720110337.55384-1-lianux.mm@gmail.com \
--to=lianux.mm@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=david@redhat.com \
--cc=gkwang@linx-info.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ludovico.zy.wu@gmail.com \
--cc=p1ucky0923@gmail.com \
--cc=ryncsn@gmail.com \
--cc=shuah@kernel.org \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
--cc=zijing.zhang@proton.me \
--cc=ziy@nvidia.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 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.