From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: mazziesaccount@gmail.com, Guenter Roeck <linux@roeck-us.net>,
heikki.haikola@fi.rohmeurope.com,
mikko.mutanen@fi.rohmeurope.com, lee.jones@linaro.org,
robh+dt@kernel.org, mark.rutland@arm.com,
gregkh@linuxfoundation.org, rafael@kernel.org,
mturquette@baylibre.com, sboyd@kernel.org,
linus.walleij@linaro.org, bgolaszewski@baylibre.com,
sre@kernel.org, lgirdwood@gmail.com, a.zummo@towertech.it,
alexandre.belloni@bootlin.com, wim@linux-watchdog.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-pm@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-watchdog@vger.kernel.org, bogdan-petru.chircu-mare@nxp.com
Subject: Re: [PATCH v10 0/9] support ROHM BD70528 PMIC
Date: Thu, 28 Feb 2019 11:40:26 +0000 [thread overview]
Message-ID: <20190228114026.GA6802@sirena.org.uk> (raw)
In-Reply-To: <20190228070450.GB3773@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On Thu, Feb 28, 2019 at 09:04:50AM +0200, Matti Vaittinen wrote:
> On Thu, Feb 14, 2019 at 03:02:37PM +0200, Matti Vaittinen wrote:
>> Patch series introducing support for ROHM BD70528 PMIC
>
> I was wondering if there is anything that could be done to allow the MFD
> part of this series to end up in upstream without having to wait the
> regmap-irq changes
> (https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git/commit/?h=topic/irq)
> to be merged from Linus' tree to MFD tree? If I see it correctly, the
> regmap-irq (main-irq-reg support) changes are not targeted to linux 5.1.
> To me it looks like getting them to MFD via Linus' tree will take a while.
They're targeted for v5.1 and I sent a pull request to Lee for that
branch IIRC.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-28 11:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 13:02 [PATCH v10 0/9] support ROHM BD70528 PMIC Matti Vaittinen
2019-02-14 13:04 ` [PATCH v10 1/9] mfd: regulator: clk: split rohm-bd718x7.h Matti Vaittinen
2019-02-14 13:05 ` [PATCH v10 2/9] mfd: bd70528: Support ROHM bd70528 PMIC - core Matti Vaittinen
2019-02-14 13:07 ` [PATCH v10 3/9] clk: bd718x7: Support ROHM BD70528 clk block Matti Vaittinen
2019-02-14 13:08 ` [PATCH v10 4/9] devicetree: bindings: Document first ROHM BD70528 bindings Matti Vaittinen
2019-02-14 13:09 ` [PATCH v10 5/9] gpio: Initial support for ROHM bd70528 GPIO block Matti Vaittinen
2019-02-14 13:10 ` [PATCH v10 6/9] rtc: bd70528: Initial support for ROHM bd70528 RTC Matti Vaittinen
2019-02-14 13:11 ` [PATCH v10 7/9] power: supply: Initial support for ROHM BD70528 PMIC charger block Matti Vaittinen
2019-02-14 13:12 ` [PATCH v10 8/9] watchdog: bd70528: Initial support for ROHM BD70528 watchdog block Matti Vaittinen
2019-02-14 14:16 ` Guenter Roeck
2019-02-14 13:15 ` [PATCH v10 9/9] regulator: bd70528: drop struct bd70528 Matti Vaittinen
2019-02-28 7:04 ` [PATCH v10 0/9] support ROHM BD70528 PMIC Matti Vaittinen
2019-02-28 8:10 ` Lee Jones
2019-02-28 8:22 ` Matti Vaittinen
2019-03-25 7:36 ` Matti Vaittinen
2019-03-25 8:02 ` Lee Jones
2019-03-25 8:20 ` Matti Vaittinen
2019-02-28 11:40 ` Mark Brown [this message]
2019-03-06 10:38 ` Matti Vaittinen
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=20190228114026.GA6802@sirena.org.uk \
--to=broonie@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=bgolaszewski@baylibre.com \
--cc=bogdan-petru.chircu-mare@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.haikola@fi.rohmeurope.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=mikko.mutanen@fi.rohmeurope.com \
--cc=mturquette@baylibre.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sre@kernel.org \
--cc=wim@linux-watchdog.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).