public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: WANG Rui <r@hev.cc>
To: lance.yang@linux.dev
Cc: baolin.wang@linux.alibaba.com, brauner@kernel.org,
	david@kernel.org, jack@suse.cz, kees@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, r@hev.cc, usama.arif@linux.dev,
	viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: [PATCH v5] binfmt_elf: Align eligible read-only PT_LOAD segments to PMD_SIZE for THP
Date: Sun, 15 Mar 2026 12:10:05 +0800	[thread overview]
Message-ID: <20260315041005.11682-1-r@hev.cc> (raw)
In-Reply-To: <20260315034647.8462-1-lance.yang@linux.dev>

Hi Lance,

> It would be better to keep earlier CC list across revisions, especially
> for people who have already reviewed or were explicitly include before.
> Otherwise, they may simply never see subsequent revisions, and from
> their side the discussion just stops there ...

Thanks for pointing this out.

After addressing David's feedback on v4 [1], v5 no longer looked
mm-related to me, so I only sent it to linux-fsdevel.

But you're right, I should have kept the earlier CC list, especially
for people who had already reviewed it or were CC'ed explicitly in the
previous rounds.

[1] https://lore.kernel.org/linux-fsdevel/60ba4311-01f8-4ff3-a2df-e1b3fb6db699@kernel.org

Thanks,
Rui


  reply	other threads:[~2026-03-15  4:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13  0:52 [PATCH v5] binfmt_elf: Align eligible read-only PT_LOAD segments to PMD_SIZE for THP WANG Rui
2026-03-15  3:46 ` Lance Yang
2026-03-15  4:10   ` WANG Rui [this message]
2026-03-15 13:12   ` Usama Arif
2026-03-20 11:44     ` David Hildenbrand (Arm)
2026-03-20 17:11       ` WANG Rui
2026-03-21 14:21         ` WANG Rui

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=20260315041005.11682-1-r@hev.cc \
    --to=r@hev.cc \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=brauner@kernel.org \
    --cc=david@kernel.org \
    --cc=jack@suse.cz \
    --cc=kees@kernel.org \
    --cc=lance.yang@linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=usama.arif@linux.dev \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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