From: Mark Brown <broonie@kernel.org>
To: Markuss Broks <markuss.broks@gmail.com>
Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org,
lee.jones@linaro.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/5] dt-bindings: regulator: Add bindings for Silicon Mitus SM5703 regulators
Date: Fri, 29 Apr 2022 13:03:08 +0100 [thread overview]
Message-ID: <YmvT/LL+1jB8xK77@sirena.org.uk> (raw)
In-Reply-To: <2a18073b-974f-00d4-5811-8df577e943a8@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
On Fri, Apr 29, 2022 at 02:51:03PM +0300, Markuss Broks wrote:
> On 4/29/22 14:48, Mark Brown wrote:
> > As Rob said please send an incremental patch with any fixes needed.
> I'm sorry, I didn't understand it correctly. Does "incremental patch" mean I
> should send a separate follow-up patch with those fixes?
Yes. It means on top of what's already applied.
Please also don't label patches that aren't part of a patch series as
though they were in a series, it just creates confusion.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-04-29 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 11:39 [PATCH v6 2/5] dt-bindings: regulator: Add bindings for Silicon Mitus SM5703 regulators Markuss Broks
2022-04-29 11:48 ` Mark Brown
2022-04-29 11:51 ` Markuss Broks
2022-04-29 12:03 ` 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=YmvT/LL+1jB8xK77@sirena.org.uk \
--to=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markuss.broks@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=phone-devel@vger.kernel.org \
--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).