From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kuldeep Singh <singh.kuldeep87k@gmail.com>,
Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v2 3/3] ARM: dts: aspeed: Remove arch timer clocks property
Date: Fri, 18 Mar 2022 14:44:05 +0100 [thread overview]
Message-ID: <ad56b5bc-a9d4-b584-3c04-7c47995381f1@kernel.org> (raw)
In-Reply-To: <20220317191527.96237-4-singh.kuldeep87k@gmail.com>
On 17/03/2022 20:15, Kuldeep Singh wrote:
>
> Moreover, clocks also matches incorrectly with the regex pattern.
> Remove this entry altogether to fix it.
> 'clocks' does not match any of the regexes: 'pinctrl-[0-9]+'
Except of ongoing discussion, this paragraph is incorrect. There is no
incorrect match of regex pattern. The field is simply not documented in
the bindings (not allowed by bindings). This paragraph is actually
confusing and misleading.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-03-18 13:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 19:15 [PATCH v2 0/3] Fix for arch timer users Kuldeep Singh
2022-03-17 19:15 ` [PATCH v2 1/3] dt-bindings: timer: Rearrange compatible entries of arch timer Kuldeep Singh
2022-03-17 19:15 ` [PATCH v2 2/3] dt-bindings: timer: Document arm,cortex-a7-timer in " Kuldeep Singh
2022-03-17 20:25 ` [PATCH v2 2/3] dt-bindings: timer: Document arm, cortex-a7-timer " Robin Murphy
2022-03-17 21:25 ` Kuldeep Singh
2022-03-20 18:47 ` Rob Herring
2022-03-21 11:52 ` Robin Murphy
2022-03-23 18:35 ` Kuldeep Singh
2022-03-25 21:23 ` Rob Herring
2022-04-11 12:35 ` Geert Uytterhoeven
2022-03-17 19:15 ` [PATCH v2 3/3] ARM: dts: aspeed: Remove arch timer clocks property Kuldeep Singh
2022-03-17 19:54 ` Marc Zyngier
2022-03-17 21:10 ` Kuldeep Singh
2022-03-17 21:46 ` Marc Zyngier
2022-03-18 6:18 ` Joel Stanley
2022-03-18 13:44 ` Krzysztof Kozlowski [this message]
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=ad56b5bc-a9d4-b584-3c04-7c47995381f1@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=singh.kuldeep87k@gmail.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).