From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Anjelique Melendez <quic_amelende@quicinc.com>
Cc: corbet@lwn.net, robh+dt@kernel.org, agross@kernel.org,
andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org,
vkoul@kernel.org, linux-doc@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_collinsd@quicinc.com
Subject: Re: [RESEND PATCH v5 0/2] add support for PON GEN3 device
Date: Sun, 11 Sep 2022 14:18:43 +0200 [thread overview]
Message-ID: <20220911121843.k4appu2fszeeilkc@mercury.elektranox.org> (raw)
In-Reply-To: <20220909204207.15820-1-quic_amelende@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
Hi,
On Fri, Sep 09, 2022 at 01:42:07PM -0700, Anjelique Melendez wrote:
> Resent with fixed path for dt-bindings.
>
> Changes from v4:
> - Updated commit message for patch 1/2
>
> Changes from v3:
> - Addressed Krysztof's comments on patch 1/2
> - Added missing minItems/maxItems
> - Merged if statments with same constraints together
> - Removed description from "reg-names"
>
> Changes from v2:
> - Added new "qcom,pmk8350-pon" compatible string as per Krysztof's
> advice
> - Updated dt logic to use comptaible strings to decide constraints
> as per Krysztof's comment
> - Added new patch (v3 2/2) to support new compatible string
>
> Changes from v1:
> - Updated path which was missing Documentation/devicetree prefix
> - Updated CC list
>
> New patch series to separate this patch from applied patches.
> Comments from original patch can be found
> https://lore.kernel.org/linux-arm-msm/27515993-18f3-8891-4835-9b6a8d7f86b0@quicinc.com/
>
> David Collins (1):
> dt-bindings: power: reset: qcom-pon: Add new compatible
> "qcom,pmk8350-pon"
>
> Anjelique Melendez (1):
> power: reset: qcom-pon: add support for qcom,pmk8350-pon compatible string
>
> Documentation/devicetree/bindings/power/reset/qcom,pon.yaml | 50 +++++++++++++++++++++++++++---
> drivers/power/reset/qcom-pon.c | 1 +
> 2 file changed, 47 insertions(+), 4 deletions(-)
Thanks, I queued both patches.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-09-12 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 20:42 [RESEND PATCH v5 0/2] add support for PON GEN3 device Anjelique Melendez
2022-09-09 20:42 ` [RESEND PATCH v5 1/2] dt-bindings: power: reset: qcom-pon: Add new compatible "qcom,pmk8350-pon" Anjelique Melendez
2022-09-10 7:57 ` Krzysztof Kozlowski
2022-09-12 4:33 ` Vinod Koul
2022-09-09 20:42 ` [RESEND PATCH v5 2/2] power: reset: qcom-pon: add support for qcom,pmk8350-pon compatible string Anjelique Melendez
2022-09-10 7:57 ` Krzysztof Kozlowski
2022-09-12 4:33 ` Vinod Koul
2022-09-11 12:18 ` Sebastian Reichel [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=20220911121843.k4appu2fszeeilkc@mercury.elektranox.org \
--to=sebastian.reichel@collabora.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_amelende@quicinc.com \
--cc=quic_collinsd@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@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).