[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-1373d9c2-ae29-488e-b2c1-032ab2cd52ba@palmer-mbp2014>
Date: Wed, 10 Aug 2022 15:01:40 -0700 (PDT)
From: Palmer Dabbelt <palmer@...osinc.com>
To: Conor.Dooley@...rochip.com
CC: airlied@...ux.ie, robh+dt@...nel.org, vkoul@...nel.org,
krzysztof.kozlowski+dt@...aro.org, daniel@...ll.ch,
thierry.reding@...il.com, sam@...nborg.org,
Eugeniy.Paltsev@...opsys.com, fancer.lancer@...il.com,
daniel.lezcano@...aro.org,
Paul Walmsley <paul.walmsley@...ive.com>,
aou@...s.berkeley.edu, masahiroy@...nel.org,
damien.lemoal@...nsource.wdc.com, geert@...ux-m68k.org,
niklas.cassel@....com, dillon.minfei@...il.com,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, dmaengine@...r.kernel.org,
linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v5 00/13] Canaan devicetree fixes
On Fri, 05 Aug 2022 10:51:00 PDT (-0700), Conor.Dooley@...rochip.com wrote:
> On 14/07/2022 23:11, Conor Dooley - M52691 wrote:
>> On 14/07/2022 23:04, Palmer Dabbelt wrote:
>>> I'm trying to sort out how to merge this one. I'm not opposed to taking it through the RISC-V tree as Rob's reviewed/acked the bindings, but just figured I'd say something before putting anything on for-next to try and minimize confusion.
>>>
>>> Unless I'm missing something it's just patch 3 that's been taken so far, via Vinod's tree. I've dropped that one and put the rest on palmer/riscv-canaan_dt_schema, if that looks good then I'll take it into riscv/for-next when this loops back to the top of my queue.
>>>
>>> Thanks!
>>
>> Patches 1 & 2 never got review from the DRM side and patch 12
>> depends on those. If it comes to it, you could drop those three
>> (and patch 3 that Vinod took). The only other one is patch 4,
>> which has Krzysztof's ack as memory-controller maintainer, so
>> that one should be okay.
>
> Hey Palmer,
> These fixes have been sitting on palmer/riscv-canaan_dt_schema for
> a few weeks now, without an autobuilder complaint etc. Could you
> move it onto for-next?
These are on for-next.
Powered by blists - more mailing lists