All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zi Yan" <ziy@nvidia.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
	"Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Baolin Wang" <baolin.wang@linux.alibaba.com>,
	"Liam R. Howlett" <liam@infradead.org>,
	"Nico Pache" <nico.pache@linux.dev>,
	"Ryan Roberts" <ryan.roberts@arm.com>,
	"Dev Jain" <dev.jain@arm.com>, "Barry Song" <baohua@kernel.org>,
	"Lance Yang" <lance.yang@linux.dev>,
	"Usama Arif" <usama.arif@linux.dev>,
	"Peter Xu" <peterx@redhat.com>, "Jason Gunthorpe" <jgg@ziepe.ca>,
	<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
	"Cedric Le Goater" <clg@redhat.com>,
	"Saravanan D" <saravanand@crusoe.ai>, <stable@vger.kernel.org>
Subject: Re: [PATCH] mm/huge_memory: bypass THP tuneables for huge pfnmap mappings
Date: Mon, 07 Sep 2026 13:05:37 -0400	[thread overview]
Message-ID: <DL98XU1QOKDM.U9TLB4G5HLXY@nvidia.com> (raw)
In-Reply-To: <2732913d-dbee-4726-aaad-c7c60b6c62fb@kernel.org>

On Mon Sep 7, 2026 at 1:00 PM EDT, David Hildenbrand (Arm) wrote:
> On 9/7/26 18:58, Zi Yan wrote:
>> On Mon Sep 7, 2026 at 12:30 PM EDT, Lorenzo Stoakes (ARM) wrote:
>>> On Mon, Sep 07, 2026 at 06:19:30PM +0200, David Hildenbrand (Arm) wrote:
>> 
>> Probably worth putting it in the process documentation. Always resend if
>> a patch has any change.
>
> For things like fixes for spelling mistakes I don't really mind. So "always" is
> a strong word :)

Sure. At least a fixup could be sent as a direct reply to the original
patch. In rare cases, such fixups can become messy if more than one are
sent and a respin is better.

>
> But yes, such stuff will be documented in the future.



-- 
Best Regards,
Yan, Zi



  reply	other threads:[~2026-09-07 17:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 19:55 [PATCH] mm/huge_memory: bypass THP tuneables for huge pfnmap mappings Lorenzo Stoakes (ARM)
2026-08-28  2:52 ` Zi Yan
2026-08-28  7:11   ` Lorenzo Stoakes (ARM)
2026-09-07 16:08     ` David Hildenbrand (Arm)
2026-09-07 16:15       ` Lorenzo Stoakes (ARM)
2026-09-07 16:19         ` David Hildenbrand (Arm)
2026-09-07 16:30           ` Lorenzo Stoakes (ARM)
2026-09-07 16:58             ` Zi Yan
2026-09-07 17:00               ` David Hildenbrand (Arm)
2026-09-07 17:05                 ` Zi Yan [this message]
2026-08-28  4:47 ` Lance Yang
2026-08-28 16:46 ` Saravanan D
2026-08-28 17:20   ` Lorenzo Stoakes (ARM)
2026-08-29  0:24 ` SJ Park
2026-08-31  8:15 ` Baolin Wang
2026-09-07 16:14 ` David Hildenbrand (Arm)
2026-09-07 16:17   ` Lorenzo Stoakes (ARM)

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=DL98XU1QOKDM.U9TLB4G5HLXY@nvidia.com \
    --to=ziy@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=clg@redhat.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=jgg@ziepe.ca \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=nico.pache@linux.dev \
    --cc=peterx@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=saravanand@crusoe.ai \
    --cc=stable@vger.kernel.org \
    --cc=usama.arif@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 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.