linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Barry Song <21cnbao@gmail.com>,
	Usama Arif <usamaarif642@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Barry Song <v-songbaohua@oppo.com>,
	Chengming Zhou <chengming.zhou@linux.dev>,
	Yosry Ahmed <yosryahmed@google.com>,
	Nhat Pham <nphamcs@gmail.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Hugh Dickins <hughd@google.com>,
	Matthew Wilcox <willy@infradead.org>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Andi Kleen <ak@linux.intel.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Chris Li <chrisl@kernel.org>,
	"Huang, Ying" <ying.huang@intel.com>,
	Kairui Song <kasong@tencent.com>,
	Ryan Roberts <ryan.roberts@arm.com>
Subject: Re: [PATCH v2] mm: count zeromap read and set for swapout and swapin
Date: Tue, 5 Nov 2024 09:24:12 +0100	[thread overview]
Message-ID: <91c683e7-58dc-4518-94bb-884b11683895@redhat.com> (raw)
In-Reply-To: <942f8355-4b23-4fd9-b00e-1121552d89ee@redhat.com>

On 05.11.24 09:23, David Hildenbrand wrote:
> On 05.11.24 04:40, Andrew Morton wrote:
>> On Mon, 4 Nov 2024 13:32:55 +0100 David Hildenbrand <david@redhat.com> wrote:
>>
>>>> As mentioned above, this isn't about fixing a bug; it's simply to ensure
>>>> that swap-related metrics don't disappear.
>>>
>>> Documentation/process/submitting-patches.rst:
>>>
>>> "A Fixes: tag indicates that the patch fixes an issue in a previous
>>> commit. It is used to make it easy to determine where a bug originated,
>>> which can help review a bug fix."
>>>
>>> If there is no BUG, I'm afraid you are abusing that tag.
>>
>> I think the abuse is reasonable.  We have no Should-be-included-with:.
> 
> A "Belongs-to:" might make sense, for this kind of stuff that is still
> only in an RFC.

s/RFC/RC/

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-11-05  8:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-02 10:12 Barry Song
2024-11-02 12:32 ` Usama Arif
2024-11-02 12:59   ` Barry Song
2024-11-02 14:43     ` Usama Arif
2024-11-04 16:24       ` Joshua Hahn
2024-11-04 12:32     ` David Hildenbrand
2024-11-05  3:40       ` Andrew Morton
2024-11-05  8:23         ` David Hildenbrand
2024-11-05  8:24           ` David Hildenbrand [this message]
2024-11-05  9:15           ` Barry Song
2024-11-05 10:44             ` Usama Arif
2024-11-05 10:57               ` Barry Song
2024-11-05 11:09             ` David Hildenbrand
2024-11-04 12:42 ` David Hildenbrand
2024-11-04 16:34   ` Johannes Weiner
2024-11-04 17:10     ` David Hildenbrand
2024-11-04 18:48       ` Usama Arif
2024-11-04 20:56         ` David Hildenbrand
2024-11-04 21:24           ` Usama Arif
2024-11-05  1:28             ` Barry Song
2024-11-05 19:35 ` Nhat Pham

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=91c683e7-58dc-4518-94bb-884b11683895@redhat.com \
    --to=david@redhat.com \
    --cc=21cnbao@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=chengming.zhou@linux.dev \
    --cc=chrisl@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=kasong@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --cc=ryan.roberts@arm.com \
    --cc=shakeel.butt@linux.dev \
    --cc=usamaarif642@gmail.com \
    --cc=v-songbaohua@oppo.com \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.com \
    --cc=yosryahmed@google.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