From: "Kumar, Kaushlendra" <kaushlendra.kumar@intel.com>
To: SeongJae Park <sj@kernel.org>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: RE: [PATCH v2] tools/mm/slabinfo: fix access to null terminator in string boundary
Date: Mon, 1 Sep 2025 05:43:52 +0000 [thread overview]
Message-ID: <LV3PR11MB87687785FADA1665042BF83DF507A@LV3PR11MB8768.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250901032320.59995-1-sj@kernel.org>
> Thank you for making this change. But, it is conventional to put the above changelog on the comment section (after '---' line).
>
> [1] https://docs.kernel.org/process/submitting-patches.html#the-canonical-patch-format
>
> I think the above blank line is not really needed.
Thank you for the feedback! I have incorporated your suggestions and submitted patch V4.
This version fixes an issue that remained unresolved in V3.
BR,
Kaushlendra
prev parent reply other threads:[~2025-09-01 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 17:20 Kaushlendra Kumar
2025-09-01 3:23 ` SeongJae Park
2025-09-01 4:57 ` Kumar, Kaushlendra
2025-09-01 5:43 ` Kumar, Kaushlendra [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=LV3PR11MB87687785FADA1665042BF83DF507A@LV3PR11MB8768.namprd11.prod.outlook.com \
--to=kaushlendra.kumar@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=sj@kernel.org \
/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