From: Mark Brown <broonie@kernel.org>
To: Luca Weiss <luca@z3ntu.xyz>
Cc: linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, afd@ti.com,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/3] regulator: dt-bindings: qcom,usb-vbus-regulator: change node name
Date: Mon, 31 Oct 2022 17:45:34 +0000 [thread overview]
Message-ID: <Y2AJvt0SnHTnU7G0@sirena.org.uk> (raw)
In-Reply-To: <20221031173933.936147-2-luca@z3ntu.xyz>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
On Mon, Oct 31, 2022 at 06:39:32PM +0100, Luca Weiss wrote:
> usb-vbus-regulator is a better generic node name than dcdc to change the
> example to match.
You've not copied me on the rest of the series so I've no idea what's
going on with dependencies. When sending a patch series it is important
to ensure that all the various maintainers understand what the
relationship between the patches as the expecation is that there will be
interdependencies. Either copy everyone on the whole series or at least
copy them on the cover letter and explain what's going on. If there are
no strong interdependencies then it's generally simplest to just send
the patches separately to avoid any possible confusion.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-31 17:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 17:39 [PATCH v2 1/3] dt-bindings: mfd: qcom,spmi-pmic: support more types Luca Weiss
2022-10-31 17:39 ` [PATCH v2 2/3] regulator: dt-bindings: qcom,usb-vbus-regulator: change node name Luca Weiss
2022-10-31 17:45 ` Mark Brown [this message]
2022-11-02 10:38 ` Neil Armstrong
2022-11-02 15:41 ` Luca Weiss
2022-11-02 19:12 ` Krzysztof Kozlowski
2022-11-02 16:27 ` Rob Herring
2022-12-28 21:30 ` Luca Weiss
2022-12-29 17:57 ` Mark Brown
2022-12-29 18:11 ` Luca Weiss
2022-12-29 18:43 ` Mark Brown
2022-12-29 19:12 ` Luca Weiss
2022-10-31 17:39 ` [PATCH v2 3/3] arm64: dts: qcom: pm8150b: change vbus-regulator " Luca Weiss
2022-11-02 10:38 ` Neil Armstrong
2022-11-02 16:26 ` [PATCH v2 1/3] dt-bindings: mfd: qcom,spmi-pmic: support more types Rob Herring
2022-11-07 9:07 ` Lee Jones
2022-11-08 1:27 ` (subset) " Bjorn Andersson
2022-11-16 14:06 ` 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=Y2AJvt0SnHTnU7G0@sirena.org.uk \
--to=broonie@kernel.org \
--cc=afd@ti.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=phone-devel@vger.kernel.org \
--cc=quic_wcheng@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).