devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
Cc: "Lee Jones" <lee.jones@linaro.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Sebastian Reichel" <sre@kernel.org>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	linux-actions@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v6 4/7] regulator: Add regulator driver for ATC260x PMICs
Date: Mon, 25 Jan 2021 20:51:59 +0000	[thread overview]
Message-ID: <20210125205159.GD4510@sirena.org.uk> (raw)
In-Reply-To: <20210125205048.GA1066705@BV030612LT>

[-- Attachment #1: Type: text/plain, Size: 726 bytes --]

On Mon, Jan 25, 2021 at 10:50:48PM +0200, Cristian Ciocaltea wrote:
> On Mon, Jan 25, 2021 at 07:23:11PM +0000, Mark Brown wrote:

> > Please do not submit new versions of already applied patches, please
> > submit incremental updates to the existing code.  Modifying existing

> The patches applied to 'for-next' branches were not modified, but I have
> (wrongly) assumed I need to keep them in the series until they are
> eventually merged into master.

> So, if I understand correctly, I should have dropped them from the patch
> series as soon as they had been queued, and only if they need some
> additional work, I can re-add them as incremental updates.

Yes, once something is applied it shouldn't need sending again.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-01-25 20:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 18:23 [PATCH v6 0/7] Add initial support for ATC260x PMICs Cristian Ciocaltea
2021-01-20 18:23 ` [PATCH v6 1/7] dt-bindings: input: Add reset-time-sec common property Cristian Ciocaltea
2021-01-20 18:23 ` [PATCH v6 2/7] dt-bindings: mfd: Add Actions Semi ATC260x PMIC binding Cristian Ciocaltea
2021-01-20 18:23 ` [PATCH v6 3/7] mfd: Add MFD driver for ATC260x PMICs Cristian Ciocaltea
2021-01-25 14:25   ` Lee Jones
2021-01-25 18:47     ` Cristian Ciocaltea
2021-01-26  8:15       ` Lee Jones
2021-01-26 10:15         ` Cristian Ciocaltea
2021-01-20 18:23 ` [PATCH v6 4/7] regulator: Add regulator " Cristian Ciocaltea
2021-01-25 19:23   ` Mark Brown
2021-01-25 20:50     ` Cristian Ciocaltea
2021-01-25 20:51       ` Mark Brown [this message]
2021-01-20 18:23 ` [PATCH v6 5/7] power: reset: Add poweroff " Cristian Ciocaltea
2021-01-20 18:23 ` [PATCH v6 6/7] input: atc260x: Add onkey " Cristian Ciocaltea
2021-01-20 18:23 ` [PATCH v6 7/7] MAINTAINERS: Add entry for ATC260x PMIC Cristian Ciocaltea

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=20210125205159.GD4510@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=afaerber@suse.de \
    --cc=cristian.ciocaltea@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-actions@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=sre@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).