[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<VI1PR09MB23335FF3B1274ED13F24AF06947D2@VI1PR09MB2333.eurprd09.prod.outlook.com>
Date: Mon, 7 Oct 2024 06:17:14 +0000
From: Vladimir Kondratiev <Vladimir.Kondratiev@...ileye.com>
To: Christoph Hellwig <hch@...radead.org>
CC: Alexandre Ghiti <alex@...ti.fr>, Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
Andrew Morton <akpm@...ux-foundation.org>, "linux-riscv@...ts.infradead.org"
<linux-riscv@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH v1] riscv: make ZONE_DMA32 optional
>Well, this doesn't get any more true by just irgnoring the previous
>discussion and just reposting :(
Sorry, this wasn't the intention. Perhaps I messed with the message-id, I see my "patch v1" in one mail thread together with the previous discussion, but not in the other thread.
Anyway, I think making ZONE_DMA32 selection depend on NONPORTABLE answers the concern
that was raised
Powered by blists - more mailing lists