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: Thu, 29 Dec 2022 18:43:08 +0000 [thread overview]
Message-ID: <Y63fvNfPrnot+C6a@sirena.org.uk> (raw)
In-Reply-To: <12119923.O9o76ZdvQC@g550jk>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
On Thu, Dec 29, 2022 at 07:11:10PM +0100, Luca Weiss wrote:
> The patch was sent end of October, that is two months ago. I don't think two
> months of waiting is an unreasonable amount of time and is also more than "a
> couple of weeks"...
> And as far as I am aware there's no open review comments, which is why I did
> send the email to ask what the status is so that it can go into 6.3 and I can
> remove it from my inbox.
Please read the rest of the mail:
> > directly if something has gone wrong you'll have to resend the patches
> > anyway, so sending again is generally a better approach though there are
> > some other maintainers who like them - if in doubt look at how patches
> > for the subsystem are normally handled.
I can't do anything with your content free ping on patch 2 of
some series...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-12-29 18:43 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
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 [this message]
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=Y63fvNfPrnot+C6a@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).