From: Mark Brown <broonie@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: andersson@kernel.org, linux-arm-msm@vger.kernel.org,
krzysztof.kozlowski@linaro.org, agross@kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org, patches@linaro.org,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: regulator: qcom,smd: Document PMR735a
Date: Thu, 10 Nov 2022 12:00:57 +0000 [thread overview]
Message-ID: <Y2zn+a7eL8PnGgWo@sirena.org.uk> (raw)
In-Reply-To: <bf3e5725-8cf7-3a0e-aa9b-0b05a4507868@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
On Thu, Nov 10, 2022 at 12:09:10PM +0100, Konrad Dybcio wrote:
> On 10/11/2022 12:03, Mark Brown wrote:
> > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
> Please apply v2 instead:
> https://lore.kernel.org/linux-arm-msm/20221110091736.3344-2-konrad.dybcio@linaro.org/T/#u
As the mail you are replying to says:
> > If any updates are required or you are submitting further changes they
> > should be sent as incremental updates against current git, existing
> > patches will not be replaced.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-11-10 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 11:08 [PATCH 1/2] dt-bindings: regulator: qcom,smd: Document PMR735a Konrad Dybcio
2022-11-09 11:08 ` [PATCH 2/2] regulator: qcom_smd: Add PMR735a regulators Konrad Dybcio
2022-11-10 3:48 ` Bjorn Andersson
2022-11-09 13:50 ` [PATCH 1/2] dt-bindings: regulator: qcom,smd: Document PMR735a Krzysztof Kozlowski
2022-11-10 11:03 ` Mark Brown
2022-11-10 11:09 ` Konrad Dybcio
2022-11-10 12:00 ` Mark Brown [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=Y2zn+a7eL8PnGgWo@sirena.org.uk \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=robh+dt@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).