From: "Arnd Bergmann" <arnd@arndb.de>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>,
"Arnd Bergmann" <arnd@kernel.org>,
"Hugh Dickins" <hughd@google.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Mike Rapoport" <rppt@kernel.org>,
"Pasha Tatashin" <pasha.tatashin@soleen.com>
Cc: "Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Kairui Song" <kasong@tencent.com>,
"Christian Brauner" <brauner@kernel.org>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Kemeng Shi" <shikemeng@huaweicloud.com>,
"Guo Weikang" <guoweikang.kernel@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [v2] mm: shmem: avoid build warning for CONFIG_SHMEM=n
Date: Thu, 04 Dec 2025 11:41:50 +0100 [thread overview]
Message-ID: <998794e8-d8b3-4693-8e56-cbac0f2072f7@app.fastmail.com> (raw)
In-Reply-To: <93782526-c198-4590-b96b-c4f630b8ecbb@kernel.org>
On Thu, Dec 4, 2025, at 11:34, David Hildenbrand (Red Hat) wrote:
>
> So we can likely just squash it into the problematic commit before
> proceeding with it?
Yes, that would be best.
Arnd
next prev parent reply other threads:[~2025-12-04 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 10:28 Arnd Bergmann
2025-12-04 10:34 ` David Hildenbrand (Red Hat)
2025-12-04 10:41 ` Arnd Bergmann [this message]
2025-12-04 10:55 ` Mike Rapoport
2025-12-04 11:03 ` David Hildenbrand (Red Hat)
2025-12-04 13:34 ` Pratyush Yadav
2025-12-04 10:55 ` Mike Rapoport
2025-12-04 12:38 ` Baolin Wang
2025-12-04 13:31 ` Pratyush Yadav
2025-12-04 14:10 ` Pasha Tatashin
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=998794e8-d8b3-4693-8e56-cbac0f2072f7@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=david@kernel.org \
--cc=guoweikang.kernel@gmail.com \
--cc=hughd@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=shikemeng@huaweicloud.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