From: fffsqian <fffsqian@163.com>
To: "Muchun Song" <muchun.song@linux.dev>
Cc: 傅清爽 <fuqingshuang@kylinos.cn>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Dave Chinner" <david@fromorbit.com>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
"Qi Zheng" <qi.zheng@linux.dev>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re:Re: [PATCH 1/1] mm/shrinker: add NULL checks after rcu_dereference() in shrinker bit functions
Date: Fri, 26 Jun 2026 14:28:43 +0800 (CST) [thread overview]
Message-ID: <549d2280.4ff8.19f029dcaeb.Coremail.fffsqian@163.com> (raw)
In-Reply-To: <305C42A2-1359-4998-A95C-49998B4660DB@linux.dev>
At 2026-06-26 11:49:13, "Muchun Song" <muchun.song@linux.dev> wrote:
>
>Thanks for your contribution! I have a couple of quick suggestions to
>help things go smoother:
>
>- Please take a closer look at our community communication guidelines,
> as we rely on plain-text-based replies here.
>
>- For any issues you're not completely sure about, it would be awesome
> if you could run a quick validation yourself before sending out a patch.
> Maintainers' time is quite limited, so this helps everyone save a lot
> of energy and speeds up the review process.
>
>Thanks for understanding, and looking forward to your next patch!
>
>Thanks,
>Muchun
Hi,
Thank you very much for your kind reminders and valuable suggestions.
I will strictly follow the plain-text reply specification for all future mailing list communications.
Meanwhile, I will do more sufficient code analysis and self-verification before submitting patches to avoid inaccurate problem description and unnecessary review cost.
Looking forward to submitting more qualified patches later.
Best regards,
Qingshuang Fu
prev parent reply other threads:[~2026-06-26 6:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 9:55 [PATCH 1/1] mm/shrinker: add NULL checks after rcu_dereference() in shrinker bit functions fffsqian
2026-06-24 10:49 ` Qi Zheng
2026-06-25 3:01 ` 傅清爽
2026-06-26 3:49 ` Muchun Song
2026-06-26 6:28 ` fffsqian [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=549d2280.4ff8.19f029dcaeb.Coremail.fffsqian@163.com \
--to=fffsqian@163.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=fuqingshuang@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=qi.zheng@linux.dev \
--cc=roman.gushchin@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