From: "Rafał Miłecki" <zajec5@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: "Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Vivek Unune" <npcomplete13@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>,
"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH V3 RESEND] dt-bindings: mfd: add Broadcom CRU
Date: Mon, 16 Aug 2021 07:14:18 +0200 [thread overview]
Message-ID: <76a2cdb9-0d74-0dfc-7a78-a5c8022c643d@gmail.com> (raw)
In-Reply-To: <20210713094745.2586-1-zajec5@gmail.com>
Hi Lee,
On 13.07.2021 11:47, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> CRU is a block used in e.g. Northstar devices. It can be seen in the
> bcm5301x.dtsi and this binding documents its proper usage.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> V2: Use complete binding & change additionalProperties to false
> V3: Use clock-controller@ for clocks
> RESEND: Patch is ready for pushing now since 5.14-rc1 is out
>
> Lee: last time I sent this patch you couldn't push it because of docs
> validation dependency on 3 following commits:
> ac5f8197d15c ("dt-bindings: pinctrl: convert Broadcom Northstar to the json-schema")
> 08e9fdfbb224 ("dt-bindings: thermal: brcm,ns-thermal: Convert to the json-schema")
> 8f711f68cffd ("dt-bindings: clock: brcm, iproc-clocks: convert to the json-schema")
>
> All above commits made it into the 5.14-rc1.
let me kindly ask you about this patch as I don't see it in the
https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/log/?h=for-mfd-next
Could you send it to Linus with your upcoming 5.15 pull req, please?
next prev parent reply other threads:[~2021-08-16 5:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 9:47 [PATCH V3 RESEND] dt-bindings: mfd: add Broadcom CRU Rafał Miłecki
2021-08-16 5:14 ` Rafał Miłecki [this message]
2021-08-16 13:12 ` Lee Jones
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=76a2cdb9-0d74-0dfc-7a78-a5c8022c643d@gmail.com \
--to=zajec5@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=npcomplete13@gmail.com \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).