From: Harry Yoo <harry@kernel.org>
To: Guopeng Zhang <zhangguopeng@kylinos.cn>,
Guopeng Zhang <guopeng.zhang@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: memcg: remove stray text from obj_stock_pcp comment
Date: Wed, 24 Jun 2026 13:32:09 +0900 [thread overview]
Message-ID: <a3393f60-4ada-4768-a369-900350c97cf6@kernel.org> (raw)
In-Reply-To: <5be54565-00be-4c05-91ca-0825fa925167@kylinos.cn>
[-- Attachment #1.1: Type: text/plain, Size: 1875 bytes --]
On 6/23/26 6:02 PM, Guopeng Zhang wrote:
> 在 2026/6/23 16:42, Harry Yoo 写道:
>>
>> On 6/23/26 5:26 PM, Guopeng Zhang wrote:
>>> From: Guopeng Zhang <zhangguopeng@kylinos.cn>
>>>
>>> A patch filename was accidentally inserted into the comment describing
>>> the nr_bytes field of struct obj_stock_pcp. Remove it.
>> nit: perhaps add something like
>> "Fix a typo in the comment (target -> targets)"?
> Hi Harry,
Hi Guopeng,
> Thanks for the review and the Ack.
>
> Yes, I also fixed the "target -> targets" typo, but missed mentioning it
> in the commit message.
No worries :)
It's not a big deal, just wanted to mention.
> I'll be more careful about describing all changes
> clearly next time.
Thanks!
> If a respin is needed, I'll add it to the commit
> message and carry your Acked-by.
I guess it's okay to not respin for this.
Thanks!
> Thanks,
> Guopeng
>
>>> No functional change.
>>>
>>> Signed-off-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
>>> ---
>> FWIW,
>> Acked-by: Harry Yoo (Oracle) <harry@kernel.org>
>>
>> Thanks!
>>
>>> mm/memcontrol.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>>> index 6dc4888a90f3..3eedfc4e84a0 100644
>>> --- a/mm/memcontrol.c
>>> +++ b/mm/memcontrol.c
>>> @@ -2039,7 +2039,7 @@ struct obj_stock_pcp {
>>> /*
>>> * On rare archs with 256KiB base page size (hexagon and powerpc 44x)
>>> * keep nr_bytes to unsigned int as uint16_t cannot represent the full
>>> -e patches/memcg-uint16_t-for-nr_bytes-in-obj_stock_pcp.patch * sub-page remainder. Such archs are not cacheline optimization target.
>>> + * sub-page remainder. Such archs are not cacheline optimization targets.
>>> */
>>> unsigned int nr_bytes[NR_OBJ_STOCK];
>>> #else
--
Cheers,
Harry / Hyeonggon
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-06-24 4:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 8:26 [PATCH] mm: memcg: remove stray text from obj_stock_pcp comment Guopeng Zhang
2026-06-23 8:42 ` Harry Yoo
2026-06-23 9:02 ` Guopeng Zhang
2026-06-24 4:32 ` Harry Yoo [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=a3393f60-4ada-4768-a369-900350c97cf6@kernel.org \
--to=harry@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guopeng.zhang@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=zhangguopeng@kylinos.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