From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jassi Brar <jaswinder.singh@linaro.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh@kernel.org,
ilias.apalodimas@linaro.org, masahisa.kojima@linaro.org
Subject: Re: [PATCH] dt-bindings: arm: socionext: add bindings for the Synquacer platform
Date: Fri, 16 Jun 2023 18:47:41 +0200 [thread overview]
Message-ID: <e2b98d80-8e9a-6083-3bc5-677bef0d3263@linaro.org> (raw)
In-Reply-To: <CAJe_ZhdV3yaKUVD43duO4hkGMByJhq7x9bN+eBXJdBXdxgDneg@mail.gmail.com>
On 16/06/2023 18:23, Jassi Brar wrote:
> On Fri, 16 Jun 2023 at 05:15, Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>> On 16/06/2023 05:58, jaswinder.singh@linaro.org wrote:
>>> From: Jassi Brar <jaswinder.singh@linaro.org>
>>>
>>> Socionext's DeveloperBox is based on the SC2A11B SoC (Synquacer).
>>> Specify bindings for the platform and boards based on that.
>>
>> A nit, subject: drop second/last, redundant "bindings". The
>> "dt-bindings" prefix is already stating that these are bindings.
>>
> I can remove it, but I see many mentions like "Fix bindings for" "Add
> binding for" etc in the subject line.
Can we fix them as well?
>
>>
>> Binding without it's user is usually useless. Where is the user?
>>
> It is required for SystemReady-2.0 certification.
For what? If there is no user, it is not required for SR. We don't
document compatibles for something which does not exist in the projects.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-16 16:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 3:58 jaswinder.singh
2023-06-16 10:15 ` Krzysztof Kozlowski
2023-06-16 13:12 ` Jassi Brar
2023-06-16 10:15 ` Krzysztof Kozlowski
2023-06-16 16:23 ` Jassi Brar
2023-06-16 16:47 ` Krzysztof Kozlowski [this message]
2023-06-16 20:06 ` Jassi Brar
2023-06-16 20:34 ` Krzysztof Kozlowski
2023-06-16 23:18 ` Jassi Brar
2023-06-17 7:18 ` Krzysztof Kozlowski
2023-06-19 19:17 ` Jassi Brar
2023-06-20 6:27 ` Krzysztof Kozlowski
2023-06-20 16:50 ` Rob Herring
2023-06-20 17:08 ` Jassi Brar
2023-06-20 17:07 ` [PATCHv2] dt-bindings: arm: socionext: add Synquacer platforms jaswinder.singh
2023-06-20 17:16 ` Krzysztof Kozlowski
2023-06-20 17:24 ` Jassi Brar
2023-06-20 17:54 ` Krzysztof Kozlowski
2023-06-20 18:21 ` Jassi Brar
2023-06-21 15:36 ` [PATCHv3] " jaswinder.singh
2023-06-22 2:01 ` Rob Herring
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=e2b98d80-8e9a-6083-3bc5-677bef0d3263@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jaswinder.singh@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahisa.kojima@linaro.org \
--cc=robh@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
all inboxes | Powered by JetHome®