From: Andrew Morton <akpm@linux-foundation.org>
To: David Hildenbrand <david@redhat.com>
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: Mon, 4 Nov 2024 19:40:24 -0800 [thread overview]
Message-ID: <20241104194024.0284288a28a71a70a3eab9b0@linux-foundation.org> (raw)
In-Reply-To: <3f943f72-59d6-4124-96b2-e0bb8d7a5ebd@redhat.com>
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:.
0ca0c24e3211 is only in 6.12-rcX so this is the time to make
userspace-visible tweaks, so the 6.12 interfaces are the same as the
6.13+ interfaces (which is what I think is happening here?)
And including the Fixes in this patch might be useful to someone who is
backporting 0ca0c24e3211 into some earlier kernel for their own
purposes.
next prev parent reply other threads:[~2024-11-05 3:40 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 [this message]
2024-11-05 8:23 ` David Hildenbrand
2024-11-05 8:24 ` David Hildenbrand
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=20241104194024.0284288a28a71a70a3eab9b0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=21cnbao@gmail.com \
--cc=ak@linux.intel.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=chengming.zhou@linux.dev \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--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