From: Mark Brown <broonie@kernel.org>
To: Stefan Agner <stefan@agner.ch>
Cc: lee.jones@linaro.org, lgirdwood@gmail.com, khilman@baylibre.com,
carlo@caione.org, b.galvani@gmail.com, max.oss.09@gmail.com,
marcel@ziswiler.com, linux@armlinux.org.uk, galak@codeaurora.org,
ijc+devicetree@hellion.org.uk, mark.rutland@arm.com,
pawel.moll@arm.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 3/5] regulator: rn5t618: add RN5T567 PMIC support
Date: Mon, 6 Jun 2016 19:04:11 +0100 [thread overview]
Message-ID: <20160606180411.GG7510@sirena.org.uk> (raw)
In-Reply-To: <c6edd422420533d16c076ad5e721e549@agner.ch>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
On Mon, Jun 06, 2016 at 10:47:40AM -0700, Stefan Agner wrote:
> On 2016-06-06 10:35, Mark Brown wrote:
> > Acked-by: Mark Brown <broonie@kernel.org>
> Thanks Mark.
> Do you have an idea how the patchset should be handled with the
> dependent dt change in patch 1?
Lee will need to apply at least the first patch, I'd expect he'll also
apply this and send me a pull request (or perhaps just send me a pull
request for the MFD change).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] regulator: rn5t618: add RN5T567 PMIC support
Date: Mon, 6 Jun 2016 19:04:11 +0100 [thread overview]
Message-ID: <20160606180411.GG7510@sirena.org.uk> (raw)
In-Reply-To: <c6edd422420533d16c076ad5e721e549@agner.ch>
On Mon, Jun 06, 2016 at 10:47:40AM -0700, Stefan Agner wrote:
> On 2016-06-06 10:35, Mark Brown wrote:
> > Acked-by: Mark Brown <broonie@kernel.org>
> Thanks Mark.
> Do you have an idea how the patchset should be handled with the
> dependent dt change in patch 1?
Lee will need to apply at least the first patch, I'd expect he'll also
apply this and send me a pull request (or perhaps just send me a pull
request for the MFD change).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160606/5bd19d37/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 3/5] regulator: rn5t618: add RN5T567 PMIC support
Date: Mon, 6 Jun 2016 19:04:11 +0100 [thread overview]
Message-ID: <20160606180411.GG7510@sirena.org.uk> (raw)
In-Reply-To: <c6edd422420533d16c076ad5e721e549@agner.ch>
On Mon, Jun 06, 2016 at 10:47:40AM -0700, Stefan Agner wrote:
> On 2016-06-06 10:35, Mark Brown wrote:
> > Acked-by: Mark Brown <broonie@kernel.org>
> Thanks Mark.
> Do you have an idea how the patchset should be handled with the
> dependent dt change in patch 1?
Lee will need to apply at least the first patch, I'd expect he'll also
apply this and send me a pull request (or perhaps just send me a pull
request for the MFD change).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20160606/5bd19d37/attachment.sig>
next prev parent reply other threads:[~2016-06-06 18:04 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 0:17 [PATCH 0/5] regulator: add Ricoh RN5T567 PMIC support Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` [PATCH 1/5] ARM: dts: meson: minix-neo-x8: define PMIC as power controller Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-29 18:05 ` Applied "ARM: dts: meson: minix-neo-x8: define PMIC as power controller" to the regulator tree Mark Brown
2016-06-29 18:05 ` Mark Brown
2016-06-29 18:05 ` Mark Brown
2016-06-29 18:05 ` Mark Brown
2016-06-05 0:17 ` [PATCH 2/5] mfd: add Ricoh RN5T567 PMIC support Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` [PATCH 3/5] regulator: rn5t618: Add " Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-29 18:05 ` Applied "regulator: rn5t618: Add RN5T567 PMIC support" to the regulator tree Mark Brown
2016-06-29 18:05 ` Mark Brown
2016-06-29 18:05 ` Mark Brown
2016-06-29 18:05 ` Mark Brown
2016-06-05 0:17 ` [PATCH 3/5] regulator: rn5t618: add RN5T567 PMIC support Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-06 17:35 ` Mark Brown
2016-06-06 17:35 ` Mark Brown
2016-06-06 17:35 ` Mark Brown
2016-06-06 17:47 ` Stefan Agner
2016-06-06 17:47 ` Stefan Agner
2016-06-06 17:47 ` Stefan Agner
2016-06-06 17:47 ` Stefan Agner
2016-06-06 18:04 ` Mark Brown [this message]
2016-06-06 18:04 ` Mark Brown
2016-06-06 18:04 ` Mark Brown
2016-06-05 0:17 ` [PATCH 4/5] mfd: rn5t618: register power off callback optionally Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` [PATCH 5/5] mfd: rn5t618: register restart handler Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 0:17 ` Stefan Agner
2016-06-05 1:24 ` kbuild test robot
2016-06-05 1:24 ` kbuild test robot
2016-06-05 1:24 ` kbuild test robot
2016-06-05 1:24 ` kbuild test robot
2016-06-05 2:52 ` Stefan Agner
2016-06-05 2:52 ` Stefan Agner
2016-06-05 2:52 ` Stefan Agner
2016-06-05 2:52 ` Stefan Agner
2016-06-06 13:25 ` Marcel Ziswiler
2016-06-06 13:25 ` Marcel Ziswiler
2016-06-06 13:25 ` Marcel Ziswiler
2016-06-06 17:19 ` Stefan Agner
2016-06-06 17:19 ` Stefan Agner
2016-06-06 17:19 ` Stefan Agner
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=20160606180411.GG7510@sirena.org.uk \
--to=broonie@kernel.org \
--cc=b.galvani@gmail.com \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@baylibre.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcel@ziswiler.com \
--cc=mark.rutland@arm.com \
--cc=max.oss.09@gmail.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefan@agner.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.