From: <Conor.Dooley@microchip.com>
To: <palmer@rivosinc.com>
Cc: <airlied@linux.ie>, <robh+dt@kernel.org>, <vkoul@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <daniel@ffwll.ch>,
<thierry.reding@gmail.com>, <sam@ravnborg.org>,
<Eugeniy.Paltsev@synopsys.com>, <fancer.lancer@gmail.com>,
<daniel.lezcano@linaro.org>, <paul.walmsley@sifive.com>,
<aou@eecs.berkeley.edu>, <masahiroy@kernel.org>,
<damien.lemoal@opensource.wdc.com>, <geert@linux-m68k.org>,
<niklas.cassel@wdc.com>, <dillon.minfei@gmail.com>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v5 00/13] Canaan devicetree fixes
Date: Fri, 5 Aug 2022 17:51:00 +0000 [thread overview]
Message-ID: <338e4fd5-9d6d-6f83-30fb-3ab3ed0ead31@microchip.com> (raw)
In-Reply-To: <e8d235f3-fdf0-891e-1f9f-387c6e6af7da@microchip.com>
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?
Would be nice to clear these up for 6.0 :)
Thanks,
Conor.
WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <palmer@rivosinc.com>
Cc: <airlied@linux.ie>, <robh+dt@kernel.org>, <vkoul@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <daniel@ffwll.ch>,
<thierry.reding@gmail.com>, <sam@ravnborg.org>,
<Eugeniy.Paltsev@synopsys.com>, <fancer.lancer@gmail.com>,
<daniel.lezcano@linaro.org>, <paul.walmsley@sifive.com>,
<aou@eecs.berkeley.edu>, <masahiroy@kernel.org>,
<damien.lemoal@opensource.wdc.com>, <geert@linux-m68k.org>,
<niklas.cassel@wdc.com>, <dillon.minfei@gmail.com>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v5 00/13] Canaan devicetree fixes
Date: Fri, 5 Aug 2022 17:51:00 +0000 [thread overview]
Message-ID: <338e4fd5-9d6d-6f83-30fb-3ab3ed0ead31@microchip.com> (raw)
In-Reply-To: <e8d235f3-fdf0-891e-1f9f-387c6e6af7da@microchip.com>
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?
Would be nice to clear these up for 6.0 :)
Thanks,
Conor.
_______________________________________________
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: <Conor.Dooley@microchip.com>
To: <palmer@rivosinc.com>
Cc: niklas.cassel@wdc.com, airlied@linux.ie,
dri-devel@lists.freedesktop.org, thierry.reding@gmail.com,
krzysztof.kozlowski+dt@linaro.org,
linux-riscv@lists.infradead.org, sam@ravnborg.org,
masahiroy@kernel.org, daniel.lezcano@linaro.org,
geert@linux-m68k.org, Eugeniy.Paltsev@synopsys.com,
devicetree@vger.kernel.org, aou@eecs.berkeley.edu,
robh+dt@kernel.org, paul.walmsley@sifive.com,
dillon.minfei@gmail.com, linux-kernel@vger.kernel.org,
fancer.lancer@gmail.com, vkoul@kernel.org,
dmaengine@vger.kernel.org, damien.lemoal@opensource.wdc.com
Subject: Re: [PATCH v5 00/13] Canaan devicetree fixes
Date: Fri, 5 Aug 2022 17:51:00 +0000 [thread overview]
Message-ID: <338e4fd5-9d6d-6f83-30fb-3ab3ed0ead31@microchip.com> (raw)
In-Reply-To: <e8d235f3-fdf0-891e-1f9f-387c6e6af7da@microchip.com>
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?
Would be nice to clear these up for 6.0 :)
Thanks,
Conor.
next prev parent reply other threads:[~2022-08-05 17:51 UTC|newest]
Thread overview: 108+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 21:52 [PATCH v5 00/13] Canaan devicetree fixes Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` [PATCH v5 01/13] dt-bindings: display: convert ilitek,ili9341.txt to dt-schema Conor Dooley
2022-07-05 21:52 ` [PATCH v5 01/13] dt-bindings: display: convert ilitek, ili9341.txt " Conor Dooley
2022-07-05 21:52 ` [PATCH v5 01/13] dt-bindings: display: convert ilitek,ili9341.txt " Conor Dooley
2022-07-05 21:52 ` [PATCH v5 02/13] dt-bindings: display: ili9341: document canaan kd233's lcd Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-12 7:56 ` Conor.Dooley
2022-07-12 7:56 ` Conor.Dooley
2022-07-12 7:56 ` Conor.Dooley
2022-07-05 21:52 ` [PATCH v5 03/13] dt-bindings: dma: dw-axi-dmac: extend the number of interrupts Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-06 5:45 ` Vinod Koul
2022-07-06 5:45 ` Vinod Koul
2022-07-06 5:45 ` Vinod Koul
2022-07-18 15:12 ` Ben Dooks
2022-07-18 15:12 ` Ben Dooks
2022-07-18 15:12 ` Ben Dooks
2022-07-18 15:23 ` Conor.Dooley
2022-07-18 15:23 ` Conor.Dooley
2022-07-18 15:23 ` Conor.Dooley
2022-07-05 21:52 ` [PATCH v5 04/13] dt-bindings: memory-controllers: add canaan k210 sram controller Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-06 14:48 ` Rob Herring
2022-07-06 14:48 ` Rob Herring
2022-07-06 14:48 ` Rob Herring
2022-07-10 19:39 ` Conor.Dooley
2022-07-10 19:39 ` Conor.Dooley
2022-07-10 19:39 ` Conor.Dooley
2022-07-10 23:21 ` Damien Le Moal
2022-07-10 23:21 ` Damien Le Moal
2022-07-10 23:21 ` Damien Le Moal
2022-07-12 15:54 ` Conor.Dooley
2022-07-12 15:54 ` Conor.Dooley
2022-07-12 15:54 ` Conor.Dooley
2022-07-12 15:59 ` Krzysztof Kozlowski
2022-07-12 15:59 ` Krzysztof Kozlowski
2022-07-12 15:59 ` Krzysztof Kozlowski
2022-07-12 16:04 ` Conor.Dooley
2022-07-12 16:04 ` Conor.Dooley
2022-07-12 16:04 ` Conor.Dooley
2022-08-16 9:27 ` Krzysztof Kozlowski
2022-08-16 9:27 ` Krzysztof Kozlowski
2022-08-16 9:27 ` Krzysztof Kozlowski
2022-08-16 9:31 ` Conor.Dooley
2022-08-16 9:31 ` Conor.Dooley
2022-08-16 9:31 ` Conor.Dooley
2022-07-05 21:52 ` [PATCH v5 05/13] riscv: dts: canaan: fix the k210's memory node Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` [PATCH v5 06/13] riscv: dts: canaan: fix the k210's timer nodes Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` [PATCH v5 07/13] riscv: dts: canaan: fix mmc node names Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` [PATCH v5 08/13] riscv: dts: canaan: fix kd233 display spi frequency Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` [PATCH v5 09/13] riscv: dts: canaan: use custom compatible for k210 i2s Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` [PATCH v5 10/13] riscv: dts: canaan: remove spi-max-frequency from controllers Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` [PATCH v5 11/13] riscv: dts: canaan: fix bus {ranges,reg} warnings Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` [PATCH v5 12/13] riscv: dts: canaan: add specific compatible for kd233's LCD Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` [PATCH v5 13/13] riscv: dts: canaan: build all devicetress if SOC_CANAAN Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-05 21:52 ` Conor Dooley
2022-07-06 8:03 ` [PATCH v5 00/13] Canaan devicetree fixes Geert Uytterhoeven
2022-07-06 8:03 ` Geert Uytterhoeven
2022-07-06 8:03 ` Geert Uytterhoeven
2022-07-06 8:21 ` Conor.Dooley
2022-07-06 8:21 ` Conor.Dooley
2022-07-06 8:21 ` Conor.Dooley
2022-07-06 11:55 ` Damien Le Moal
2022-07-06 11:55 ` Damien Le Moal
2022-07-06 11:55 ` Damien Le Moal
2022-07-06 12:01 ` Conor.Dooley
2022-07-06 12:01 ` Conor.Dooley
2022-07-06 12:01 ` Conor.Dooley
2022-07-06 8:09 ` Geert Uytterhoeven
2022-07-06 8:09 ` Geert Uytterhoeven
2022-07-06 8:09 ` Geert Uytterhoeven
2022-07-14 22:04 ` Palmer Dabbelt
2022-07-14 22:04 ` Palmer Dabbelt
2022-07-14 22:04 ` Palmer Dabbelt
2022-07-14 22:11 ` Conor.Dooley
2022-07-14 22:11 ` Conor.Dooley
2022-07-14 22:11 ` Conor.Dooley
2022-08-05 17:51 ` Conor.Dooley [this message]
2022-08-05 17:51 ` Conor.Dooley
2022-08-05 17:51 ` Conor.Dooley
2022-08-10 22:01 ` Palmer Dabbelt
2022-08-10 22:01 ` Palmer Dabbelt
2022-08-10 22:01 ` Palmer Dabbelt
2022-08-11 6:26 ` Conor.Dooley
2022-08-11 6:26 ` Conor.Dooley
2022-08-11 6:26 ` Conor.Dooley
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=338e4fd5-9d6d-6f83-30fb-3ab3ed0ead31@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=airlied@linux.ie \
--cc=aou@eecs.berkeley.edu \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel.lezcano@linaro.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dillon.minfei@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fancer.lancer@gmail.com \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=niklas.cassel@wdc.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
--cc=vkoul@kernel.org \
/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.