From: Michal Simek <michal.simek@amd.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com
Cc: "Alvin Šipraga" <alsi@bang-olufsen.dk>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Rob Herring" <robh@kernel.org>,
"Stephen Boyd" <sboyd@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:COMMON CLK FRAMEWORK" <linux-clk@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: clock: si5351: Make compatible string required property
Date: Wed, 2 Oct 2024 10:24:39 +0200 [thread overview]
Message-ID: <74e07428-2ed4-47e2-a8ef-360df0252e17@amd.com> (raw)
In-Reply-To: <fa249ec7-409f-4dee-b853-736c5de464be@kernel.org>
On 10/2/24 10:19, Krzysztof Kozlowski wrote:
> On 02/10/2024 09:51, Michal Simek wrote:
>> Compatible property is likely also required property.
>>
>> Signed-off-by: Michal Simek <michal.simek@amd.com>
>> ---
>
> That's a convention but not necessary, a no-op.
But how do you identify device then?
Or are you saying that device description is valid even if there is no
compatible string?
M
next prev parent reply other threads:[~2024-10-02 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 7:51 [PATCH] dt-bindings: clock: si5351: Make compatible string required property Michal Simek
2024-10-02 8:19 ` Krzysztof Kozlowski
2024-10-02 8:24 ` Michal Simek [this message]
2024-10-02 10:31 ` Michal Simek
2024-10-02 12:17 ` Krzysztof Kozlowski
2024-10-02 21:41 ` Rob Herring
2024-10-03 5:57 ` Michal Simek
2024-10-03 7:02 ` Krzysztof Kozlowski
2024-10-02 12:02 ` Krzysztof Kozlowski
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=74e07428-2ed4-47e2-a8ef-360df0252e17@amd.com \
--to=michal.simek@amd.com \
--cc=alsi@bang-olufsen.dk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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