From: Krzysztof Kozlowski <krzk@kernel.org>
To: Oleksii Moisieiev <Oleksii_Moisieiev@epam.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/1] dt-bindings: arm: Add scmi_devid paramter for
Date: Tue, 22 Feb 2022 12:16:40 +0100 [thread overview]
Message-ID: <e2cc06e9-df8b-696f-50c5-bea28fe53e42@kernel.org> (raw)
In-Reply-To: <20220222103022.GA496631@EPUAKYIW015D>
On 22/02/2022 11:30, Oleksii Moisieiev wrote:
> Hi Krzysztof,
>
>>>
>>> Also what do you think about maintainers: field? Is it correct? I'm not
>>> sure if I used it correctly.
>>
>>
>> I think you should add arm,scmi maintainer next to you.
>>
>
> Should I update MAINTAINERS file as well?
Yes, the bindings file should be added to the SCPI/SCMI entry. You can
just add a wildcard * to cover all files.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-02-22 11:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 17:26 [RFC PATCH 0/1] dt-bindings: arm: Add scmi_devid paramter for Oleksii Moisieiev
2022-02-21 17:26 ` [RFC PATCH 1/1] dt-bindings: arm: Add scmi_devid property description for SCMI Oleksii Moisieiev
2022-02-22 14:22 ` Rob Herring
2022-02-22 14:51 ` Oleksii Moisieiev
2022-02-22 18:25 ` Rob Herring
2022-02-21 21:01 ` [RFC PATCH 0/1] dt-bindings: arm: Add scmi_devid paramter for Krzysztof Kozlowski
2022-02-21 21:39 ` Oleksii Moisieiev
2022-02-22 8:06 ` Krzysztof Kozlowski
2022-02-22 8:55 ` Oleksii Moisieiev
2022-02-22 9:27 ` Krzysztof Kozlowski
2022-02-22 10:30 ` Oleksii Moisieiev
2022-02-22 11:16 ` Krzysztof Kozlowski [this message]
2022-02-22 13:54 ` Oleksii Moisieiev
2022-02-22 16:14 ` Sudeep Holla
2022-02-22 17:34 ` Oleksii Moisieiev
2022-02-24 2:51 ` Stefano Stabellini
2022-02-24 9:32 ` Cristian Marussi
2022-02-24 22:22 ` Stefano Stabellini
2022-03-01 14:55 ` Oleksii Moisieiev
2022-03-04 11:21 ` Sudeep Holla
2022-03-04 11:18 ` Sudeep Holla
2022-02-22 11:00 ` Cristian Marussi
2022-02-22 13:51 ` Oleksii Moisieiev
2022-02-22 16:06 ` Sudeep Holla
2022-02-22 17:15 ` Oleksii Moisieiev
2022-02-24 11:54 ` Sudeep Holla
2022-02-24 22:51 ` Stefano Stabellini
2022-02-24 23:34 ` Stefano Stabellini
2022-03-04 11:12 ` Sudeep Holla
2022-03-05 0:45 ` Stefano Stabellini
2022-04-29 21:46 ` Rob Herring
2022-03-01 16:10 ` Oleksii Moisieiev
2022-03-01 16:05 ` Oleksii Moisieiev
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=e2cc06e9-df8b-696f-50c5-bea28fe53e42@kernel.org \
--to=krzk@kernel.org \
--cc=Oleksii_Moisieiev@epam.com \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sstabellini@kernel.org \
--cc=sudeep.holla@arm.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).