From: Johan Hovold <johan@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] dt-bindings: spmi: clean up hisilicon binding
Date: Tue, 19 Dec 2023 16:53:48 +0100 [thread overview]
Message-ID: <ZYG8jA64drRFL-SW@hovoldconsulting.com> (raw)
In-Reply-To: <20231130173757.13011-1-johan+linaro@kernel.org>
Hi Stephen,
On Thu, Nov 30, 2023 at 06:37:55PM +0100, Johan Hovold wrote:
> When reviewing the various SPMI PMIC bindings, I noticed that several
> examples were incorrect and misleading and could also use some cleanup.
>
> This series addresses the related hisilicon SPMI controller binding.
> Johan Hovold (2):
> dt-bindings: spmi: hisilicon,hisi-spmi-controller: fix binding
> references
> dt-bindings: spmi: hisilicon,hisi-spmi-controller: clean up example
I noticed that these are not yet in linux-next so sending a reminder.
Johan
next prev parent reply other threads:[~2023-12-19 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 17:37 [PATCH 0/2] dt-bindings: spmi: clean up hisilicon binding Johan Hovold
2023-11-30 17:37 ` [PATCH 1/2] dt-bindings: spmi: hisilicon,hisi-spmi-controller: fix binding references Johan Hovold
2023-12-01 8:29 ` Krzysztof Kozlowski
2024-04-08 3:07 ` Stephen Boyd
2023-11-30 17:37 ` [PATCH 2/2] dt-bindings: spmi: hisilicon,hisi-spmi-controller: clean up example Johan Hovold
2023-12-01 8:29 ` Krzysztof Kozlowski
2024-04-08 3:08 ` Stephen Boyd
2023-12-19 15:53 ` Johan Hovold [this message]
2024-01-26 8:29 ` [PATCH 0/2] dt-bindings: spmi: clean up hisilicon binding Johan Hovold
2024-02-29 8:13 ` Johan Hovold
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=ZYG8jA64drRFL-SW@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.