From: Michael Riesch <michael.riesch@wolfvision.net>
To: "Rob Herring" <robh+dt@kernel.org>, "Heiko Stübner" <heiko@sntech.de>
Cc: devicetree-compiler@vger.kernel.org,
David Gibson <david@gibson.dropbear.id.au>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH] checks: relax graph checks for overlays
Date: Tue, 9 Jul 2024 13:01:02 +0200 [thread overview]
Message-ID: <41277501-fcaf-428f-806b-0bf85714a1ba@wolfvision.net> (raw)
In-Reply-To: <CAL_JsqJ3rc3+OiZ7o0JNxRGnCinDQJeau6oF0TBYx3ZNcnK6-A@mail.gmail.com>
Hi David,
On 6/25/24 22:15, Rob Herring wrote:
> On Tue, Jun 18, 2024 at 2:04 PM Heiko Stübner <heiko@sntech.de> wrote:
>>
>> Hey dt and dtc people :-) ,
>>
>> Am Dienstag, 4. Juni 2024, 16:48:46 CEST schrieb Michael Riesch:
>>> This is a gentle ping with David and the DT maintainers in Cc: (I am not
>>> sure what the protocol is here, so I'll simply give this a try).
>>
>> it would be really great if someone could look at the patch and tell us
>> if that is the right direction to go, or something else needs to be done
>> instead.
>
> It is similar to other fixes in this area, so I guess it is the right
> direction. I don't really like disabling checks, but don't have a
> better suggestion.
>
> Not much else I can do here, it's up to David to pick this up.
>
> Rob
Any comments from your side? Or are you going to apply this anyway and I
should just be patient ;-)
BTW would you prefer a pull request on GitHub?
Thanks and regards,
Michael
next prev parent reply other threads:[~2024-07-09 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 14:32 [PATCH] checks: relax graph checks for overlays Michael Riesch
2024-06-04 14:48 ` Michael Riesch
2024-06-18 20:04 ` Heiko Stübner
2024-06-25 20:15 ` Rob Herring
2024-07-09 11:01 ` Michael Riesch [this message]
2024-07-29 22:39 ` Javier Carrasco
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=41277501-fcaf-428f-806b-0bf85714a1ba@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=conor+dt@kernel.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=robh+dt@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).