From: Drew Fustini <dfustini@tenstorrent.com>
To: Vladimir Kondratiev <Vladimir.Kondratiev@mobileye.com>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v1] riscv: make ZONE_DMA32 optional
Date: Sun, 6 Oct 2024 15:58:16 -0700 [thread overview]
Message-ID: <ZwMWCNYUwrW0oWVn@x1> (raw)
In-Reply-To: <VI1PR09MB233370D7BD8553E7891EF46F947C2@VI1PR09MB2333.eurprd09.prod.outlook.com>
On Sun, Oct 06, 2024 at 10:55:39AM +0000, Vladimir Kondratiev wrote:
> It is not necessary any RISCV platform has ZONE_DMA32.
> Platforms that not support ZONE_DMA32 should set
> CONFIG_NONPORTABLE because lack of ZONE_DMA32
> makes such platform non-portable indeed
I think requiring CONFIG_NONPORTABLE is a good idea. However, it seems
this patch was sent as a reply to the existing discussion thread.
Thanks,
Drew
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Drew Fustini <dfustini@tenstorrent.com>
To: Vladimir Kondratiev <Vladimir.Kondratiev@mobileye.com>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v1] riscv: make ZONE_DMA32 optional
Date: Sun, 6 Oct 2024 15:58:16 -0700 [thread overview]
Message-ID: <ZwMWCNYUwrW0oWVn@x1> (raw)
In-Reply-To: <VI1PR09MB233370D7BD8553E7891EF46F947C2@VI1PR09MB2333.eurprd09.prod.outlook.com>
On Sun, Oct 06, 2024 at 10:55:39AM +0000, Vladimir Kondratiev wrote:
> It is not necessary any RISCV platform has ZONE_DMA32.
> Platforms that not support ZONE_DMA32 should set
> CONFIG_NONPORTABLE because lack of ZONE_DMA32
> makes such platform non-portable indeed
I think requiring CONFIG_NONPORTABLE is a good idea. However, it seems
this patch was sent as a reply to the existing discussion thread.
Thanks,
Drew
next prev parent reply other threads:[~2024-10-06 22:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 11:36 [PATCH] riscv: make ZONE_DMA32 optional Vladimir Kondratiev
2024-08-27 11:36 ` Vladimir Kondratiev
2024-08-27 23:10 ` Drew Fustini
2024-08-27 23:10 ` Drew Fustini
2024-09-20 8:58 ` Palmer Dabbelt
2024-09-20 8:58 ` Palmer Dabbelt
2024-09-20 13:18 ` Drew Fustini
2024-09-20 13:18 ` Drew Fustini
2024-09-23 9:46 ` Ben Dooks
2024-09-23 9:46 ` Ben Dooks
2024-09-20 14:04 ` Christoph Hellwig
2024-09-20 14:04 ` Christoph Hellwig
2024-09-22 10:06 ` Vladimir Kondratiev
2024-09-22 10:06 ` Vladimir Kondratiev
2024-09-24 6:39 ` Christoph Hellwig
2024-09-24 6:39 ` Christoph Hellwig
2024-09-30 9:55 ` Alexandre Ghiti
2024-09-30 9:55 ` Alexandre Ghiti
2024-10-06 10:44 ` Vladimir Kondratiev
2024-10-06 10:44 ` Vladimir Kondratiev
2024-10-06 10:55 ` [PATCH v1] " Vladimir Kondratiev
2024-10-06 10:55 ` Vladimir Kondratiev
2024-10-06 22:58 ` Drew Fustini [this message]
2024-10-06 22:58 ` Drew Fustini
2024-10-07 5:41 ` Christoph Hellwig
2024-10-07 5:41 ` Christoph Hellwig
2024-10-07 6:17 ` Vladimir Kondratiev
2024-10-07 6:17 ` Vladimir Kondratiev
2024-10-07 6:22 ` Christoph Hellwig
2024-10-07 6:22 ` Christoph Hellwig
2024-10-07 11:39 ` Nick Kossifidis
2024-10-07 11:39 ` Nick Kossifidis
2024-10-07 13:03 ` Vladimir Kondratiev
2024-10-07 13:03 ` Vladimir Kondratiev
2024-10-07 12:17 ` [PATCH] " Ben Dooks
2024-10-07 12:17 ` Ben Dooks
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=ZwMWCNYUwrW0oWVn@x1 \
--to=dfustini@tenstorrent.com \
--cc=Vladimir.Kondratiev@mobileye.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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.