From: <Conor.Dooley@microchip.com>
To: <krzysztof.kozlowski@linaro.org>, <mail@conchuod.ie>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<andrew@lunn.ch>, <support.opensource@diasemi.com>,
<lee.jones@linaro.org>, <ulf.hansson@linaro.org>,
<palmer@dabbelt.com>, <paul.walmsley@sifive.com>,
<aou@eecs.berkeley.edu>, <stwiss.opensource@diasemi.com>
Cc: <linux-i2c@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mmc@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <atulkhare@rivosinc.com>
Subject: Re: [PATCH v1 0/6] clear riscv dtbs_check errors
Date: Mon, 6 Jun 2022 08:56:33 +0000 [thread overview]
Message-ID: <65293aa6-be67-cf8f-08c3-ee7e43300a88@microchip.com> (raw)
In-Reply-To: <a83be47b-4cba-e397-51ba-c2093fa0d46c@linaro.org>
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@conchuod.ie wrote:
>> From: Conor Dooley <conor.dooley@microchip.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.
next prev parent reply other threads:[~2022-06-06 8:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 13:32 [PATCH v1 0/6] clear riscv dtbs_check errors mail
2022-06-05 13:32 ` [PATCH v1 1/6] dt-bindings: mmc: convert mmc-spi-slot to yaml mail
2022-06-06 7:34 ` Krzysztof Kozlowski
2022-06-05 13:32 ` [PATCH v1 2/6] dt-bindings: i2c: convert ocores binding " mail
2022-06-06 8:02 ` Krzysztof Kozlowski
2022-06-06 14:41 ` Conor.Dooley
2022-06-06 12:53 ` Rob Herring
2022-06-05 13:32 ` [PATCH v1 3/6] MAINTAINERS: convert ocores i2c dt-binding " mail
2022-06-05 13:32 ` [PATCH v1 4/6] dt-bindings: mfd: convert da9063 " mail
2022-06-06 13:11 ` Krzysztof Kozlowski
2022-06-05 13:33 ` [PATCH v1 5/6] MAINTAINERS: " mail
2022-06-05 13:33 ` [PATCH v1 6/6] riscv: dts: sifive: "fix" pmic watchdog node name mail
2022-06-06 8:07 ` Krzysztof Kozlowski
2022-06-06 7:34 ` [PATCH v1 0/6] clear riscv dtbs_check errors Krzysztof Kozlowski
2022-06-06 8:56 ` Conor.Dooley [this message]
2022-06-08 22:27 ` Atul Khare
2022-06-08 22:42 ` 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=65293aa6-be67-cf8f-08c3-ee7e43300a88@microchip.com \
--to=conor.dooley@microchip.com \
--cc=andrew@lunn.ch \
--cc=aou@eecs.berkeley.edu \
--cc=atulkhare@rivosinc.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mail@conchuod.ie \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=stwiss.opensource@diasemi.com \
--cc=support.opensource@diasemi.com \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).