[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <9CCE7638-91FE-4B1F-9EAC-17362C041CE9@flygoat.com>
Date: Tue, 28 Mar 2023 14:02:12 +0100
From: Jiaxun Yang <jiaxun.yang@...goat.com>
To: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Cc: Christoph Hellwig <hch@....de>,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
mpe@...erman.id.au, paul.walmsley@...ive.com, palmer@...belt.com,
Rob Herring <robh+dt@...nel.org>, m.szyprowski@...sung.com,
Robin Murphy <robin.murphy@....com>,
linux-riscv@...ts.infradead.org, devicetree@...r.kernel.org,
frowand.list@...il.com
Subject: Re: [PATCH v3 0/4] Use dma_default_coherent for devicetree default
coherency
> 2023年3月28日 08:45,Thomas Bogendoerfer <tsbogend@...ha.franken.de> 写道:
>
> On Tue, Mar 28, 2023 at 03:18:12AM +0200, Christoph Hellwig wrote:
>> On Fri, Mar 24, 2023 at 09:17:38AM +0000, Jiaxun Yang wrote:
>>>>
>>>> Is patch a 6.3 candidate or should all of it go into 6.4?
>>>
>>> Please leave it for 6.4, as corresponding MIPS arch part will be a part of 6.4.
>>
>> Ok. I'll really need review from the MIPS and drivers/of/ maintainers,
>> through.
+cc devicetree foks.
>
> I don't see any MIPS changes in the series besides the ifdef CONFIG_MIPS
> part in patch 1, which gets removed again in patch 4 (chance to drop
> that completely ?).
It was suggested by DMA folks to have that patch.
> I've merged the corresponding MIPS patches into mips-next last week.
Thanks
- Jiaxun
>
> Thomas.
>
> --
> Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
> good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists