From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Yassine Oudjana <yassine.oudjana@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: Yassine Oudjana <y.oudjana@protonmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 2/3] dt-bindings: soc: mediatek: scpsys: Document MT6735 SCPSYS compatible string
Date: Mon, 27 Feb 2023 09:15:36 +0100 [thread overview]
Message-ID: <33806330-a274-c102-8b47-4b8a25422d38@linaro.org> (raw)
In-Reply-To: <20230225101629.264206-3-y.oudjana@protonmail.com>
On 25/02/2023 11:16, Yassine Oudjana wrote:
> From: Yassine Oudjana <y.oudjana@protonmail.com>
>
> Add a compatible string for MT6735 SCPSYS.
>
> Signed-off-by: Yassine Oudjana <y.oudjana@protonmail.com>
> ---
> Documentation/devicetree/bindings/soc/mediatek/scpsys.txt | 2 ++
Previous commit should be part of this one. It is logically the same and
you cannot merge them via different trees/branches.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-27 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 10:16 [PATCH 0/3] MediaTek MT6735 SCPSYS support Yassine Oudjana
2023-02-25 10:16 ` [PATCH 1/3] dt-bindings: power: Add bindings for MediaTek MT6735 Yassine Oudjana
2023-02-27 8:14 ` Krzysztof Kozlowski
2023-02-25 10:16 ` [PATCH 2/3] dt-bindings: soc: mediatek: scpsys: Document MT6735 SCPSYS compatible string Yassine Oudjana
2023-02-27 8:15 ` Krzysztof Kozlowski [this message]
2023-02-27 9:33 ` AngeloGioacchino Del Regno
2023-02-25 10:16 ` [PATCH 3/3] soc: mediatek: scpsys: Add support for MT6735 Yassine Oudjana
2023-02-27 9:33 ` AngeloGioacchino Del Regno
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=33806330-a274-c102-8b47-4b8a25422d38@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=y.oudjana@protonmail.com \
--cc=yassine.oudjana@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
all inboxes | Powered by JetHome®