From: Mark Brown <broonie@kernel.org>
To: Claudiu.Beznea@microchip.com
Cc: lgirdwood@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
Ludovic.Desroches@microchip.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/5] add PM functionality for act8945a PMIC
Date: Thu, 13 Dec 2018 15:19:13 +0000 [thread overview]
Message-ID: <20181213151913.GL10669@sirena.org.uk> (raw)
In-Reply-To: <0291f79e-b8df-f7ae-1ded-cacd404bc5fc@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
On Thu, Dec 13, 2018 at 12:59:00PM +0000, Claudiu.Beznea@microchip.com wrote:
> Hi Mark,
>
> I saw that previous version of this series was applied to your tree just
> after I've send this new one. The only difference b/w them is in the
> documentation patch where I moved the new header. No functionality change.
>
> Sorry for the noise,
No problem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-12-13 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 12:49 Claudiu.Beznea
2018-12-13 12:49 ` [PATCH v4 1/6] regulator: act8945a-regulator: unlock expert registers Claudiu.Beznea
2018-12-13 12:49 ` [PATCH v4 2/6] regulator: add documentation for regulator modes and suspend states Claudiu.Beznea
2018-12-13 12:49 ` [PATCH v4 3/6] regulator: act8945a-regulator: Implement PM functionalities Claudiu.Beznea
2018-12-13 12:49 ` [PATCH v4 4/6] regulator: act8945a-regulator: fix line over 80 chars warning Claudiu.Beznea
2018-12-13 12:50 ` [PATCH v4 5/6] regulator: act8945a-regulator: add shutdown function Claudiu.Beznea
2018-12-13 12:50 ` [PATCH v4 6/6] ARM: dts: at91: sama5d2_xplained: Add proper regulator states for suspend-to-mem Claudiu.Beznea
2018-12-13 12:59 ` [PATCH v4 0/5] add PM functionality for act8945a PMIC Claudiu.Beznea
2018-12-13 15:19 ` 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=20181213151913.GL10669@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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
all inboxes | Powered by JetHome®