[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <998794e8-d8b3-4693-8e56-cbac0f2072f7@app.fastmail.com>
Date: Thu, 04 Dec 2025 11:41:50 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "David Hildenbrand (Red Hat)" <david@...nel.org>,
"Arnd Bergmann" <arnd@...nel.org>, "Hugh Dickins" <hughd@...gle.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Pratyush Yadav" <pratyush@...nel.org>, "Mike Rapoport" <rppt@...nel.org>,
"Pasha Tatashin" <pasha.tatashin@...een.com>
Cc: "Baolin Wang" <baolin.wang@...ux.alibaba.com>,
"Kairui Song" <kasong@...cent.com>, "Christian Brauner" <brauner@...nel.org>,
"Lorenzo Stoakes" <lorenzo.stoakes@...cle.com>,
"Kemeng Shi" <shikemeng@...weicloud.com>,
"Guo Weikang" <guoweikang.kernel@...il.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [v2] mm: shmem: avoid build warning for CONFIG_SHMEM=n
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
Powered by blists - more mailing lists