From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Konrad Dybcio <konrad.dybcio@somainline.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-remoteproc@vger.kernel.org,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, Yu Chen <chenyu56@huawei.com>,
Vinod Koul <vkoul@kernel.org>, Andy Gross <agross@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Binghui Wang <wangbinghui@hisilicon.com>,
linux-phy@lists.infradead.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Carvalho Chehab <mchehab+huawei@kernel.org>,
Lee Jones <lee@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] mfd/phy/remoteproc: dt-bindings: syscon: be specific
Date: Mon, 12 Sep 2022 13:29:41 -0500 [thread overview]
Message-ID: <20220912182941.GA1596070-robh@kernel.org> (raw)
In-Reply-To: <20220817142246.828762-1-krzysztof.kozlowski@linaro.org>
On Wed, 17 Aug 2022 17:22:42 +0300, Krzysztof Kozlowski wrote:
> Hi,
>
> The last MFD/syscon patch depends on the previous ones to avoid
> dt_binding_check warnings.
>
> I propose to take entire set via Rob's DT tree.
This may have been in the window where PW server moved and stopped
getting patches, so I missed it until patch 4 got applied and broke
linux-next...
>
> Best regards,
> Krzysztof
>
> Krzysztof Kozlowski (4):
> dt-bindings: phy: hisilicon,hi3660-usb3: simplify example
> dt-bindings: phy: hisilicon,hi3670-usb3: simplify example
> dt-bindings: remoteproc: qcom,pil-info: add missing imem compatible
> dt-bindings: mfd: syscon: require specific compatible also for
> simple-mfd
I applied patches 1-3, thanks!
Rob
prev parent reply other threads:[~2022-09-12 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 14:22 [PATCH 0/4] mfd/phy/remoteproc: dt-bindings: syscon: be specific Krzysztof Kozlowski
2022-08-17 14:22 ` [PATCH 1/4] dt-bindings: phy: hisilicon,hi3660-usb3: simplify example Krzysztof Kozlowski
2022-09-02 17:25 ` Vinod Koul
2022-09-05 6:21 ` Mauro Carvalho Chehab
2022-08-17 14:22 ` [PATCH 2/4] dt-bindings: phy: hisilicon,hi3670-usb3: " Krzysztof Kozlowski
2022-09-02 17:26 ` Vinod Koul
2022-09-05 6:19 ` Mauro Carvalho Chehab
2022-08-17 14:22 ` [PATCH 3/4] dt-bindings: remoteproc: qcom,pil-info: add missing imem compatible Krzysztof Kozlowski
2022-08-17 14:22 ` [PATCH 4/4] dt-bindings: mfd: syscon: require specific compatible also for simple-mfd Krzysztof Kozlowski
2022-09-05 14:40 ` Lee Jones
2022-09-12 18:29 ` Rob Herring [this message]
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=20220912182941.GA1596070-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=chenyu56@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=wangbinghui@hisilicon.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).