[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 6 Jun 2022 08:56:33 +0000
From: <Conor.Dooley@...rochip.com>
To: <krzysztof.kozlowski@...aro.org>, <mail@...chuod.ie>,
<robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
<andrew@...n.ch>, <support.opensource@...semi.com>,
<lee.jones@...aro.org>, <ulf.hansson@...aro.org>,
<palmer@...belt.com>, <paul.walmsley@...ive.com>,
<aou@...s.berkeley.edu>, <stwiss.opensource@...semi.com>
CC: <linux-i2c@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-mmc@...r.kernel.org>,
<linux-riscv@...ts.infradead.org>, <atulkhare@...osinc.com>
Subject: Re: [PATCH v1 0/6] clear riscv dtbs_check errors
On 06/06/2022 08:34, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 05/06/2022 15:32, mail@...chuod.ie wrote:
>> From: Conor Dooley <conor.dooley@...rochip.com>
>>
>> Hey,
>> Couple conversions from txt to yaml here with the intent of fixing the
>> the dtbs_check warnings for riscv. Atul Khare already sent patches for
>> the gpio-line-names & cache-sets (which went awol) and will clear the
>> remaining two errors.
>>
>> Rob/Krzysztof:
>> Have I correctly expressed the mutually exclusive properties?
>> I had a look around, but wasn't able to find an obvious binding to ape.
>
> I'll take a look.
As always, thanks for your feedback Krzysztof.
>
>>
>> Wasn't sure if a txt -> yaml conversion's MAINTAINERS update was meant
>> to be in the same patch or not, so feel free to squash.
>
> It's the same patch, so please squash with next release.
Sure, willdo for v2.
Thanks,
Conor.
Powered by blists - more mailing lists