From: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: mazziesaccount@gmail.com, Guenter Roeck <linux@roeck-us.net>,
heikki.haikola@fi.rohmeurope.com,
mikko.mutanen@fi.rohmeurope.com, robh+dt@kernel.org,
mark.rutland@arm.com, broonie@kernel.org,
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: Mon, 25 Mar 2019 09:36:41 +0200 [thread overview]
Message-ID: <20190325073640.GB6208@localhost.localdomain> (raw)
In-Reply-To: <20190228082248.GC3773@localhost.localdomain>
Hello again Lee & all,
On Thu, Feb 28, 2019 at 10:22:48AM +0200, Matti Vaittinen wrote:
> On Thu, Feb 28, 2019 at 08:10:55AM +0000, Lee Jones wrote:
> > On Thu, 28 Feb 2019, Matti Vaittinen wrote:
> >
> > > Hello Lee and Mark,
> > >
> > > On Thu, Feb 14, 2019 at 03:02:37PM +0200, Matti Vaittinen wrote:
> > > > Patch series introducing support for ROHM BD70528 PMIC
//snip
> > >
> > > The MFD part depends on the regmap-irq changes and I think that most
> > > other subsystems want to have the MFD changes in before taking rest of
> > > the driver in their trees. So it will be a while untill all the changes
> > > are in. It would really be nice to have the drive in-tree sooner - hence
> > > I ask if theres a way. (I don't want to push, just ask if it is possible :])
> >
> > It's possible, so long as there aren't any build-time dependencies
> > between the subsystems. Immediate acceptance however isn't possible
> > due to the impending merge-window which opens in 3 days.
>
> Thanks for reply Lee. So merge-window is opening - meaning the 5.1 is
> being baked now(?)
>
> Anyays to make it clear - there is build time dependency between MFD and
> regmap-irq changes. MFD part won't compile without the changes in regmap
> tree. And theres no new Kconfig to depend on or other compile time
> checks. So REGMAP changes are required for this MFD portion to compile.
//snip
> Rest of the subsystems (regulator, clk, watchdog, gpio) do all depend on
> MFD - but they should have 'depends on' KConfig to MFD meaning they
> won't be built without MFD.
I see the 5.1-rc1 and 5.1-rc2 are out. Those contain the regmap-irq
changes the BD70528 MFD driver depends on. Would you like me to rebase
the series to some other tree (which tree/branch? I don't see updated
for-mfd-next branch in kernel.org yet) and resend it? Original patch
series was created on top of the regulator tree.
Br,
Matti Vaittinen
--
Matti Vaittinen, Linux device drivers
ROHM Semiconductors, Finland SWDC
Kiviharjunlenkki 1E
90220 OULU
FINLAND
~~~ "I don't think so," said Rene Descartes. Just then he vanished ~~~
next prev parent reply other threads:[~2019-03-25 7:36 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 [this message]
2019-03-25 8:02 ` Lee Jones
2019-03-25 8:20 ` Matti Vaittinen
2019-02-28 11:40 ` Mark Brown
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=20190325073640.GB6208@localhost.localdomain \
--to=matti.vaittinen@fi.rohmeurope.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=bgolaszewski@baylibre.com \
--cc=bogdan-petru.chircu-mare@nxp.com \
--cc=broonie@kernel.org \
--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=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).