From: <Conor.Dooley@microchip.com>
To: <sudeep.holla@arm.com>, <Niklas.Cassel@wdc.com>
Cc: <mail@conchuod.ie>, <airlied@linux.ie>, <daniel@ffwll.ch>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<thierry.reding@gmail.com>, <sam@ravnborg.org>,
<Eugeniy.Paltsev@synopsys.com>, <vkoul@kernel.org>,
<lgirdwood@gmail.com>, <broonie@kernel.org>,
<fancer.lancer@gmail.com>, <daniel.lezcano@linaro.org>,
<palmer@dabbelt.com>, <palmer@rivosinc.com>, <tglx@linutronix.de>,
<paul.walmsley@sifive.com>, <aou@eecs.berkeley.edu>,
<masahiroy@kernel.org>, <damien.lemoal@opensource.wdc.com>,
<geert@linux-m68k.org>, <dillon.minfei@gmail.com>,
<joabreu@synopsys.com>, <dri-devel@lists.freedesktop.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<dmaengine@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<linux-spi@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v3 00/15] Canaan devicetree fixes
Date: Thu, 30 Jun 2022 18:01:09 +0000 [thread overview]
Message-ID: <d0634053-d882-fcb5-fd56-32dfbcf4d5ba@microchip.com> (raw)
In-Reply-To: <20220630175318.g2zmu6ek7l5iakve@bogus>
On 30/06/2022 18:53, Sudeep Holla wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Thu, Jun 30, 2022 at 04:28:26PM +0000, Niklas Cassel wrote:
>> On Wed, Jun 29, 2022 at 07:43:29PM +0100, Conor Dooley wrote:
>>> From: Conor Dooley <conor.dooley@microchip.com>
>>>
>>> Hey all,
>>> This series should rid us of dtbs_check errors for the RISC-V Canaan k210
>>> based boards. To make keeping it that way a little easier, I changed the
>>> Canaan devicetree Makefile so that it would build all of the devicetrees
>>> in the directory if SOC_CANAAN.
>>>
>>> I *DO NOT* have any Canaan hardware so I have not tested any of this in
>>> action. Since I sent v1, I tried to buy some since it's cheap - but could
>>> out of the limited stockists none seemed to want to deliver to Ireland :(
>>> I based the series on next-20220617.
>>>
>>
>> I first tried to apply your series on top of next-20220630,
>> but was greeted by a bunch of different warnings on boot,
>> including endless RCU stall warnings.
>> However, even when booting next-20220630 without your patches,
>> I got the same warnings and RCU stall.
>>
>
> Is it possible to share the boot logs please ?
> Conor is having issues with my arch_topology/cacheinfo updates in -next.
> I would like to know if your issue is related to that or not ?
>
>> So I tested your series on top of v5.19-rc4 +
>> commit 0397d50f4cad ("spi: dt-bindings: Move 'rx-sample-delay-ns' to
>> spi-peripheral-props.yaml") cherry-picked,
>> (in order to avoid conflicts when applying your series,)
>> and the board was working as intended, no warnings or RCU stalls.
>>
>
> If possible can you give this branch[1] a try where my changes are and doesn't
> have any other changes from -next. Sorry to bother you.
>
> Conor seem to have issue with this commit[2], so if you get issues try to
> check if [3] works.
FWIW, my problems with that are not on canaan hw.
Thanks,
Conor.
>
> Regards,
> Sudeep
>
> [1] https://git.kernel.org/sudeep.holla/c/ae85abf284e7
> [2] https://git.kernel.org/sudeep.holla/c/155bd845d17b
> [3] https://git.kernel.org/sudeep.holla/c/009297d29faa
WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <sudeep.holla@arm.com>, <Niklas.Cassel@wdc.com>
Cc: alsa-devel@alsa-project.org, airlied@linux.ie,
palmer@rivosinc.com, linux-kernel@vger.kernel.org,
thierry.reding@gmail.com, krzysztof.kozlowski+dt@linaro.org,
linux-riscv@lists.infradead.org, sam@ravnborg.org,
damien.lemoal@opensource.wdc.com, daniel.lezcano@linaro.org,
joabreu@synopsys.com, geert@linux-m68k.org,
Eugeniy.Paltsev@synopsys.com, devicetree@vger.kernel.org,
aou@eecs.berkeley.edu, broonie@kernel.org,
dri-devel@lists.freedesktop.org, paul.walmsley@sifive.com,
mail@conchuod.ie, tglx@linutronix.de, dillon.minfei@gmail.com,
lgirdwood@gmail.com, fancer.lancer@gmail.com,
linux-spi@vger.kernel.org, vkoul@kernel.org, robh+dt@kernel.org,
palmer@dabbelt.com, dmaengine@vger.kernel.org,
masahiroy@kernel.org
Subject: Re: [PATCH v3 00/15] Canaan devicetree fixes
Date: Thu, 30 Jun 2022 18:01:09 +0000 [thread overview]
Message-ID: <d0634053-d882-fcb5-fd56-32dfbcf4d5ba@microchip.com> (raw)
In-Reply-To: <20220630175318.g2zmu6ek7l5iakve@bogus>
On 30/06/2022 18:53, Sudeep Holla wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Thu, Jun 30, 2022 at 04:28:26PM +0000, Niklas Cassel wrote:
>> On Wed, Jun 29, 2022 at 07:43:29PM +0100, Conor Dooley wrote:
>>> From: Conor Dooley <conor.dooley@microchip.com>
>>>
>>> Hey all,
>>> This series should rid us of dtbs_check errors for the RISC-V Canaan k210
>>> based boards. To make keeping it that way a little easier, I changed the
>>> Canaan devicetree Makefile so that it would build all of the devicetrees
>>> in the directory if SOC_CANAAN.
>>>
>>> I *DO NOT* have any Canaan hardware so I have not tested any of this in
>>> action. Since I sent v1, I tried to buy some since it's cheap - but could
>>> out of the limited stockists none seemed to want to deliver to Ireland :(
>>> I based the series on next-20220617.
>>>
>>
>> I first tried to apply your series on top of next-20220630,
>> but was greeted by a bunch of different warnings on boot,
>> including endless RCU stall warnings.
>> However, even when booting next-20220630 without your patches,
>> I got the same warnings and RCU stall.
>>
>
> Is it possible to share the boot logs please ?
> Conor is having issues with my arch_topology/cacheinfo updates in -next.
> I would like to know if your issue is related to that or not ?
>
>> So I tested your series on top of v5.19-rc4 +
>> commit 0397d50f4cad ("spi: dt-bindings: Move 'rx-sample-delay-ns' to
>> spi-peripheral-props.yaml") cherry-picked,
>> (in order to avoid conflicts when applying your series,)
>> and the board was working as intended, no warnings or RCU stalls.
>>
>
> If possible can you give this branch[1] a try where my changes are and doesn't
> have any other changes from -next. Sorry to bother you.
>
> Conor seem to have issue with this commit[2], so if you get issues try to
> check if [3] works.
FWIW, my problems with that are not on canaan hw.
Thanks,
Conor.
>
> Regards,
> Sudeep
>
> [1] https://git.kernel.org/sudeep.holla/c/ae85abf284e7
> [2] https://git.kernel.org/sudeep.holla/c/155bd845d17b
> [3] https://git.kernel.org/sudeep.holla/c/009297d29faa
WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <sudeep.holla@arm.com>, <Niklas.Cassel@wdc.com>
Cc: <mail@conchuod.ie>, <airlied@linux.ie>, <daniel@ffwll.ch>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<thierry.reding@gmail.com>, <sam@ravnborg.org>,
<Eugeniy.Paltsev@synopsys.com>, <vkoul@kernel.org>,
<lgirdwood@gmail.com>, <broonie@kernel.org>,
<fancer.lancer@gmail.com>, <daniel.lezcano@linaro.org>,
<palmer@dabbelt.com>, <palmer@rivosinc.com>, <tglx@linutronix.de>,
<paul.walmsley@sifive.com>, <aou@eecs.berkeley.edu>,
<masahiroy@kernel.org>, <damien.lemoal@opensource.wdc.com>,
<geert@linux-m68k.org>, <dillon.minfei@gmail.com>,
<joabreu@synopsys.com>, <dri-devel@lists.freedesktop.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<dmaengine@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<linux-spi@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v3 00/15] Canaan devicetree fixes
Date: Thu, 30 Jun 2022 18:01:09 +0000 [thread overview]
Message-ID: <d0634053-d882-fcb5-fd56-32dfbcf4d5ba@microchip.com> (raw)
In-Reply-To: <20220630175318.g2zmu6ek7l5iakve@bogus>
On 30/06/2022 18:53, Sudeep Holla wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Thu, Jun 30, 2022 at 04:28:26PM +0000, Niklas Cassel wrote:
>> On Wed, Jun 29, 2022 at 07:43:29PM +0100, Conor Dooley wrote:
>>> From: Conor Dooley <conor.dooley@microchip.com>
>>>
>>> Hey all,
>>> This series should rid us of dtbs_check errors for the RISC-V Canaan k210
>>> based boards. To make keeping it that way a little easier, I changed the
>>> Canaan devicetree Makefile so that it would build all of the devicetrees
>>> in the directory if SOC_CANAAN.
>>>
>>> I *DO NOT* have any Canaan hardware so I have not tested any of this in
>>> action. Since I sent v1, I tried to buy some since it's cheap - but could
>>> out of the limited stockists none seemed to want to deliver to Ireland :(
>>> I based the series on next-20220617.
>>>
>>
>> I first tried to apply your series on top of next-20220630,
>> but was greeted by a bunch of different warnings on boot,
>> including endless RCU stall warnings.
>> However, even when booting next-20220630 without your patches,
>> I got the same warnings and RCU stall.
>>
>
> Is it possible to share the boot logs please ?
> Conor is having issues with my arch_topology/cacheinfo updates in -next.
> I would like to know if your issue is related to that or not ?
>
>> So I tested your series on top of v5.19-rc4 +
>> commit 0397d50f4cad ("spi: dt-bindings: Move 'rx-sample-delay-ns' to
>> spi-peripheral-props.yaml") cherry-picked,
>> (in order to avoid conflicts when applying your series,)
>> and the board was working as intended, no warnings or RCU stalls.
>>
>
> If possible can you give this branch[1] a try where my changes are and doesn't
> have any other changes from -next. Sorry to bother you.
>
> Conor seem to have issue with this commit[2], so if you get issues try to
> check if [3] works.
FWIW, my problems with that are not on canaan hw.
Thanks,
Conor.
>
> Regards,
> Sudeep
>
> [1] https://git.kernel.org/sudeep.holla/c/ae85abf284e7
> [2] https://git.kernel.org/sudeep.holla/c/155bd845d17b
> [3] https://git.kernel.org/sudeep.holla/c/009297d29faa
_______________________________________________
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: <sudeep.holla@arm.com>, <Niklas.Cassel@wdc.com>
Cc: alsa-devel@alsa-project.org, airlied@linux.ie,
palmer@rivosinc.com, linux-kernel@vger.kernel.org,
thierry.reding@gmail.com, krzysztof.kozlowski+dt@linaro.org,
linux-riscv@lists.infradead.org, sam@ravnborg.org,
damien.lemoal@opensource.wdc.com, daniel.lezcano@linaro.org,
joabreu@synopsys.com, geert@linux-m68k.org,
Eugeniy.Paltsev@synopsys.com, devicetree@vger.kernel.org,
aou@eecs.berkeley.edu, broonie@kernel.org,
dri-devel@lists.freedesktop.org, paul.walmsley@sifive.com,
mail@conchuod.ie, tglx@linutronix.de, dillon.minfei@gmail.com,
lgirdwood@gmail.com, fancer.lancer@gmail.com,
linux-spi@vger.kernel.org, vkoul@kernel.org, robh+dt@kernel.org,
palmer@dabbelt.com, daniel@ffwll.ch, dmaengine@vger.kernel.org,
masahiroy@kernel.org
Subject: Re: [PATCH v3 00/15] Canaan devicetree fixes
Date: Thu, 30 Jun 2022 18:01:09 +0000 [thread overview]
Message-ID: <d0634053-d882-fcb5-fd56-32dfbcf4d5ba@microchip.com> (raw)
In-Reply-To: <20220630175318.g2zmu6ek7l5iakve@bogus>
On 30/06/2022 18:53, Sudeep Holla wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Thu, Jun 30, 2022 at 04:28:26PM +0000, Niklas Cassel wrote:
>> On Wed, Jun 29, 2022 at 07:43:29PM +0100, Conor Dooley wrote:
>>> From: Conor Dooley <conor.dooley@microchip.com>
>>>
>>> Hey all,
>>> This series should rid us of dtbs_check errors for the RISC-V Canaan k210
>>> based boards. To make keeping it that way a little easier, I changed the
>>> Canaan devicetree Makefile so that it would build all of the devicetrees
>>> in the directory if SOC_CANAAN.
>>>
>>> I *DO NOT* have any Canaan hardware so I have not tested any of this in
>>> action. Since I sent v1, I tried to buy some since it's cheap - but could
>>> out of the limited stockists none seemed to want to deliver to Ireland :(
>>> I based the series on next-20220617.
>>>
>>
>> I first tried to apply your series on top of next-20220630,
>> but was greeted by a bunch of different warnings on boot,
>> including endless RCU stall warnings.
>> However, even when booting next-20220630 without your patches,
>> I got the same warnings and RCU stall.
>>
>
> Is it possible to share the boot logs please ?
> Conor is having issues with my arch_topology/cacheinfo updates in -next.
> I would like to know if your issue is related to that or not ?
>
>> So I tested your series on top of v5.19-rc4 +
>> commit 0397d50f4cad ("spi: dt-bindings: Move 'rx-sample-delay-ns' to
>> spi-peripheral-props.yaml") cherry-picked,
>> (in order to avoid conflicts when applying your series,)
>> and the board was working as intended, no warnings or RCU stalls.
>>
>
> If possible can you give this branch[1] a try where my changes are and doesn't
> have any other changes from -next. Sorry to bother you.
>
> Conor seem to have issue with this commit[2], so if you get issues try to
> check if [3] works.
FWIW, my problems with that are not on canaan hw.
Thanks,
Conor.
>
> Regards,
> Sudeep
>
> [1] https://git.kernel.org/sudeep.holla/c/ae85abf284e7
> [2] https://git.kernel.org/sudeep.holla/c/155bd845d17b
> [3] https://git.kernel.org/sudeep.holla/c/009297d29faa
next prev parent reply other threads:[~2022-06-30 18:01 UTC|newest]
Thread overview: 127+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 18:43 [PATCH v3 00/15] Canaan devicetree fixes Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` [PATCH v3 01/15] dt-bindings: display: convert ilitek,ili9341.txt to dt-schema Conor Dooley
2022-06-29 18:43 ` [PATCH v3 01/15] dt-bindings: display: convert ilitek, ili9341.txt " Conor Dooley
2022-06-29 18:43 ` [PATCH v3 01/15] dt-bindings: display: convert ilitek,ili9341.txt " Conor Dooley
2022-06-29 18:43 ` [PATCH v3 02/15] dt-bindings: display: ili9341: document canaan kd233's lcd Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-07-01 19:38 ` Rob Herring
2022-07-01 19:38 ` Rob Herring
2022-07-01 19:38 ` Rob Herring
2022-07-01 19:38 ` Rob Herring
2022-06-29 18:43 ` [PATCH v3 03/15] ASoC: dt-bindings: convert designware-i2s to dt-schema Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-07-01 19:39 ` Rob Herring
2022-07-01 19:39 ` Rob Herring
2022-07-01 19:39 ` Rob Herring
2022-07-01 19:39 ` Rob Herring
2022-06-29 18:43 ` [PATCH v3 04/15] spi: dt-bindings: dw-apb-ssi: update spi-{r,t}x-bus-width Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` [PATCH v3 04/15] spi: dt-bindings: dw-apb-ssi: update spi-{r, t}x-bus-width Conor Dooley
2022-06-30 16:57 ` [PATCH v3 04/15] spi: dt-bindings: dw-apb-ssi: update spi-{r,t}x-bus-width Rob Herring
2022-06-30 16:57 ` Rob Herring
2022-06-30 16:57 ` Rob Herring
2022-06-30 16:57 ` Rob Herring
2022-06-30 21:43 ` Serge Semin
2022-06-30 21:43 ` Serge Semin
2022-06-30 21:43 ` Serge Semin
2022-06-30 21:43 ` Serge Semin
2022-06-29 18:43 ` [PATCH v3 05/15] dt-bindings: dma: dw-axi-dmac: extend the number of interrupts Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-30 21:55 ` Serge Semin
2022-06-30 21:55 ` Serge Semin
2022-06-30 21:55 ` Serge Semin
2022-06-30 21:55 ` Serge Semin
2022-06-30 23:12 ` Conor.Dooley
2022-06-30 23:12 ` Conor.Dooley
2022-06-30 23:12 ` Conor.Dooley
2022-06-30 23:12 ` Conor.Dooley
2022-07-01 19:41 ` Rob Herring
2022-07-01 19:41 ` Rob Herring
2022-07-01 19:41 ` Rob Herring
2022-07-01 19:41 ` Rob Herring
2022-06-29 18:43 ` [PATCH v3 06/15] dt-bindings: memory-controllers: add canaan k210 sram controller Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` [PATCH v3 07/15] riscv: dts: canaan: fix the k210's memory node Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` [PATCH v3 08/15] riscv: dts: canaan: fix the k210's timer nodes Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-30 21:51 ` Serge Semin
2022-06-30 21:51 ` Serge Semin
2022-06-30 21:51 ` Serge Semin
2022-06-30 21:51 ` Serge Semin
2022-06-29 18:43 ` [PATCH v3 09/15] riscv: dts: canaan: fix mmc node names Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` [PATCH v3 10/15] riscv: dts: canaan: fix kd233 display spi frequency Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` [PATCH v3 11/15] riscv: dts: canaan: use custom compatible for k210 i2s Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` [PATCH v3 12/15] riscv: dts: canaan: remove spi-max-frequency from controllers Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` [PATCH v3 13/15] riscv: dts: canaan: fix bus {ranges,reg} warnings Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-30 16:49 ` Niklas Cassel
2022-06-30 16:49 ` Niklas Cassel
2022-06-30 16:49 ` Niklas Cassel
2022-06-30 16:49 ` Niklas Cassel
2022-06-30 17:02 ` Conor.Dooley
2022-06-30 17:02 ` Conor.Dooley
2022-06-30 17:02 ` Conor.Dooley
2022-06-30 17:02 ` Conor.Dooley
2022-06-30 19:31 ` Conor.Dooley
2022-06-30 19:31 ` Conor.Dooley
2022-06-30 19:31 ` Conor.Dooley
2022-06-30 19:31 ` Conor.Dooley
2022-06-29 18:43 ` [PATCH v3 14/15] riscv: dts: canaan: add specific compatible for kd233's LCD Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` [PATCH v3 15/15] riscv: dts: canaan: build all devicetress if SOC_CANAAN Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-29 18:43 ` Conor Dooley
2022-06-30 16:28 ` [PATCH v3 00/15] Canaan devicetree fixes Niklas Cassel
2022-06-30 16:28 ` Niklas Cassel
2022-06-30 16:28 ` Niklas Cassel
2022-06-30 16:28 ` Niklas Cassel
2022-06-30 16:38 ` Conor.Dooley
2022-06-30 16:38 ` Conor.Dooley
2022-06-30 16:38 ` Conor.Dooley
2022-06-30 16:38 ` Conor.Dooley
2022-06-30 17:53 ` Sudeep Holla
2022-06-30 17:53 ` Sudeep Holla
2022-06-30 17:53 ` Sudeep Holla
2022-06-30 17:53 ` Sudeep Holla
2022-06-30 18:01 ` Conor.Dooley [this message]
2022-06-30 18:01 ` Conor.Dooley
2022-06-30 18:01 ` Conor.Dooley
2022-06-30 18:01 ` Conor.Dooley
2022-06-30 18:21 ` Sudeep Holla
2022-06-30 18:21 ` Sudeep Holla
2022-06-30 18:21 ` Sudeep Holla
2022-06-30 18:21 ` Sudeep Holla
2022-06-30 18:30 ` Conor.Dooley
2022-06-30 18:30 ` Conor.Dooley
2022-06-30 18:30 ` Conor.Dooley
2022-06-30 18:30 ` Conor.Dooley
2022-06-30 21:16 ` Damien Le Moal
2022-06-30 21:16 ` Damien Le Moal
2022-06-30 21:16 ` Damien Le Moal
2022-06-30 21:16 ` Damien Le Moal
2022-07-01 11:14 ` Sudeep Holla
2022-07-01 11:14 ` Sudeep Holla
2022-07-01 11:14 ` Sudeep Holla
2022-07-01 11:14 ` Sudeep Holla
2022-07-01 10:31 ` (subset) " Mark Brown
2022-07-01 10:31 ` Mark Brown
2022-07-01 10:31 ` Mark Brown
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=d0634053-d882-fcb5-fd56-32dfbcf4d5ba@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=Niklas.Cassel@wdc.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--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=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=mail@conchuod.ie \
--cc=masahiroy@kernel.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
--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.