From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: ti: align panel timings node name with dtschema
Date: Wed, 26 Jun 2024 13:47:44 +0200 [thread overview]
Message-ID: <CAMRc=Mc8ET2GneRT_PoGvffe+c5u13zAYsRr3u5P+aRzQv4CAQ@mail.gmail.com> (raw)
In-Reply-To: <171940115812.32431.4234002524799635130.b4-ty@linaro.org>
On Wed, Jun 26, 2024 at 1:26 PM Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> wrote:
>
>
> On Thu, 09 May 2024 12:48:13 +0200, Krzysztof Kozlowski wrote:
> > DT schema expects panel timings node to follow certain pattern,
> > dtbs_check warnings:
> >
> > am335x-pdu001.dtb: display-timings: '240x320p16' does not match any of the regexes: '^timing', 'pinctrl-[0-9]+'
> >
> > Linux drivers do not care about node name, so this should not have
> > effect on Linux.
> >
> > [...]
>
> 1.5 months on the lists, but maybe I combined too many separate TI maintainers,
> so no one feels responsible... then I guess I will take it.
>
Yeah next time you should probably at least split omap and davinci
bits into separate patches. Otherwise I think Tony thought I'd pick it
up and vice versa.
Bart
next prev parent reply other threads:[~2024-06-26 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 10:48 [PATCH] ARM: dts: ti: align panel timings node name with dtschema Krzysztof Kozlowski
2024-05-09 13:09 ` Bartosz Golaszewski
2024-06-26 11:26 ` Krzysztof Kozlowski
2024-06-26 11:47 ` Bartosz Golaszewski [this message]
2024-06-26 13:02 ` Krzysztof Kozlowski
2024-07-09 0:21 ` Kevin Hilman
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='CAMRc=Mc8ET2GneRT_PoGvffe+c5u13zAYsRr3u5P+aRzQv4CAQ@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=bcousson@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tony@atomide.com \
/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).