linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Nico Pache <npache@redhat.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	 Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	 Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Zi Yan <ziy@nvidia.com>,
	 Baolin Wang <baolin.wang@linux.alibaba.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	 Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
	Barry Song <baohua@kernel.org>,
	 Lance Yang <lance.yang@linux.dev>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] mm: khugepaged: make scan loops suspend aware
Date: Thu, 12 Feb 2026 10:51:06 +0900	[thread overview]
Message-ID: <lrouiwimacvr5o426vbxx7ucroh4etk47abfgpopmi3qcaufkr@vaiqngpotvdr> (raw)
In-Reply-To: <CAA1CXcA-V7FtK-QkyRHak1GBtepiFiTHFtF7g93P7mM41_2LMw@mail.gmail.com>

On (26/02/10 23:15), Nico Pache wrote:
> - We usually send "To:" the mailing lists and "CC:" to all other people.
> - Your subject contains "PATCHv2" there should be a space there
> - It would be worth noting the "HOW" in the commit message

Ack.


  reply	other threads:[~2026-02-12  1:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  3:15 Sergey Senozhatsky
2026-02-11  6:15 ` Nico Pache
2026-02-12  1:51   ` Sergey Senozhatsky [this message]
2026-02-11  9:50 ` David Hildenbrand (Arm)
2026-02-12  1:50   ` Sergey Senozhatsky
2026-02-12  8:30     ` David Hildenbrand (Arm)
2026-02-12  8:42       ` Sergey Senozhatsky
2026-02-12  6:32   ` Sergey Senozhatsky
2026-02-12  8:44     ` David Hildenbrand (Arm)
2026-02-12  9:05       ` Sergey Senozhatsky
2026-02-12  9:10         ` David Hildenbrand (Arm)
2026-02-12  9:24           ` Sergey Senozhatsky
2026-02-14  6:35           ` Lance Yang
2026-02-16  9:24             ` David Hildenbrand (Arm)
2026-02-16  9:50               ` Sergey Senozhatsky
2026-02-16 10:05                 ` Sergey Senozhatsky

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=lrouiwimacvr5o426vbxx7ucroh4etk47abfgpopmi3qcaufkr@vaiqngpotvdr \
    --to=senozhatsky@chromium.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=lance.yang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=npache@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=ziy@nvidia.com \
    /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