From: Andrew Morton <akpm@linux-foundation.org>
To: Zi Yan <ziy@nvidia.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"\"Matthew Wilcox (Oracle)\"" <willy@infradead.org>,
David Hildenbrand <david@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Muchun Song <muchun.song@linux.dev>,
"\"Mike Rapoport (IBM)\"" <rppt@kernel.org>,
stable@vger.kernel.org, Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH v3 1/5] mm/cma: use nth_page() in place of direct struct page manipulation.
Date: Thu, 14 Sep 2023 12:05:04 -0700 [thread overview]
Message-ID: <20230914120504.b9bbed45e3b2f59b94e87587@linux-foundation.org> (raw)
In-Reply-To: <5C626EBA-B115-4A95-8D55-5EE28C872419@nvidia.com>
On Wed, 13 Sep 2023 22:16:45 -0400 Zi Yan <ziy@nvidia.com> wrote:
> No related bug is reported. The fix comes from code
> inspection.
OK, thanks. Given that none of these appear urgent, I'll move the
series from the 6.6-rcX queue (mm-hotfixes-unstable) and into the
6.7-rc1 queue (mm-unstable), while retaining the cc:stable. To give
them more testing time before landing in mainline and -stable kernels.
next prev parent reply other threads:[~2023-09-14 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 20:12 [PATCH v3 0/5] Use nth_page() in place of direct struct page manipulation Zi Yan
2023-09-13 20:12 ` [PATCH v3 1/5] mm/cma: use " Zi Yan
2023-09-14 2:16 ` Zi Yan
2023-09-14 19:05 ` Andrew Morton [this message]
2023-09-13 20:12 ` [PATCH v3 2/5] mm/hugetlb: " Zi Yan
2023-09-14 2:20 ` Zi Yan
2023-09-13 20:12 ` [PATCH v3 3/5] mm/memory_hotplug: use pfn math " Zi Yan
2023-09-14 2:35 ` Zi Yan
2023-09-13 20:12 ` [PATCH v3 4/5] fs: use nth_page() " Zi Yan
2023-09-14 2:45 ` [PATCH v3 4/5] " Zi Yan
2023-09-13 20:12 ` [PATCH v3 5/5] mips: " Zi Yan
2023-09-14 2:46 ` Zi Yan
2023-09-13 21:12 ` [PATCH v3 0/5] Use " Andrew Morton
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=20230914120504.b9bbed45e3b2f59b94e87587@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=stable@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=willy@infradead.org \
--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 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.