linux-kernel - Re: [PATCH v10 0/9] support ROHM BD70528 PMIC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 25 Mar 2019 09:36:41 +0200
From:   Matti Vaittinen <matti.vaittinen@...rohmeurope.com>
To:     Lee Jones <lee.jones@...aro.org>
Cc:     mazziesaccount@...il.com, Guenter Roeck <linux@...ck-us.net>,
        heikki.haikola@...rohmeurope.com, mikko.mutanen@...rohmeurope.com,
        robh+dt@...nel.org, mark.rutland@....com, broonie@...nel.org,
        gregkh@...uxfoundation.org, rafael@...nel.org,
        mturquette@...libre.com, sboyd@...nel.org,
        linus.walleij@...aro.org, bgolaszewski@...libre.com,
        sre@...nel.org, lgirdwood@...il.com, a.zummo@...ertech.it,
        alexandre.belloni@...tlin.com, wim@...ux-watchdog.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-clk@...r.kernel.org, linux-gpio@...r.kernel.org,
        linux-pm@...r.kernel.org, linux-rtc@...r.kernel.org,
        linux-watchdog@...r.kernel.org, bogdan-petru.chircu-mare@....com
Subject: Re: [PATCH v10 0/9] support ROHM BD70528 PMIC

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 ~~~