linux-kernel - Re: [GIT PULL] Immutable branch between MFD, Clock, GPIO, Regulator and RTC due for the v5.13 merge window

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]

Message-ID: <43131cbebdd04a3abc51e05de5170c583006e2d2.camel@fi.rohmeurope.com>
Date:   Wed, 14 Apr 2021 17:09:53 +0000
From:   "Vaittinen, Matti" <Matti.Vaittinen@...rohmeurope.com>
To:     "lee.jones@...aro.org" <lee.jones@...aro.org>
CC:     "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-rtc@...r.kernel.org" <linux-rtc@...r.kernel.org>,
        "a.zummo@...ertech.it" <a.zummo@...ertech.it>,
        "broonie@...nel.org" <broonie@...nel.org>,
        "sboyd@...nel.org" <sboyd@...nel.org>,
        "linus.walleij@...aro.org" <linus.walleij@...aro.org>,
        "bgolaszewski@...libre.com" <bgolaszewski@...libre.com>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        linux-power <linux-power@...rohmeurope.com>,
        "alexandre.belloni@...tlin.com" <alexandre.belloni@...tlin.com>,
        "lgirdwood@...il.com" <lgirdwood@...il.com>,
        "mturquette@...libre.com" <mturquette@...libre.com>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>
Subject: Re: [GIT PULL] Immutable branch between MFD, Clock, GPIO, Regulator
 and RTC due for the v5.13 merge window

Hello Lee, Mark, Stephen, Linus, Alexandre,

On Wed, 2021-04-14 at 15:53 +0100, Lee Jones wrote:
> On Wed, 14 Apr 2021, Lee Jones wrote:
> 
> > Please note that this PR will break your build unless you have the
> > required Regulator API update.
> > 
> >  fb8fee9efdcf0 regulator: Add regmap helper for ramp-delay setting
> >  e3baacf542756 regulator: helpers: Export helper voltage listing
> 
> Looks like Mark has these:
> 
>  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator
> regulator-list-ramp-helpers
>  
> > Pull at your peril! :)
> > 
> > The following changes since commit
> > a38fd8748464831584a19438cbb3082b5a2dab15:
> > 
> >   Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
> > tags/ib-mfd-clk-gpio-regulator-rtc-v5.13
> > 
> > for you to fetch changes up to
> > 5a8a64d9a38b9d3794f9f5e153fc0358b858cc24:
> > 
> >   MAINTAINERS: Add ROHM BD71815AGW (2021-04-14 10:21:43 +0100)
> > 
> > ----------------------------------------------------------------
> > Immutable branch between MFD, Clock, GPIO, Regulator and RTC due
> > for the v5.13 merge window
> > 
> > ----------------------------------------------------------------
> > Matti Vaittinen (16):
> >       rtc: bd70528: Do not require parent data
> >       mfd: bd718x7: simplify by cleaning unnecessary device data
> >       dt_bindings: bd71828: Add clock output mode
> >       dt_bindings: regulator: Add ROHM BD71815 PMIC regulators
> >       dt_bindings: mfd: Add ROHM BD71815 PMIC
> >       mfd: Add ROHM BD71815 ID
> >       mfd: Sort ROHM chip ID list for better readability
> >       mfd: Support for ROHM BD71815 PMIC core
> >       gpio: Support ROHM BD71815 GPOs
> >       regulator: rohm-regulator: linear voltage support
> >       regulator: rohm-regulator: Support SNVS HW state.
> >       regulator: bd718x7, bd71828: Use ramp-delay helper
> >       regulator: Support ROHM BD71815 regulators
> >       clk: bd718x7: Add support for clk gate on ROHM BD71815 PMIC
> >       rtc: bd70528: Support RTC on ROHM BD71815
> >       MAINTAINERS: Add ROHM BD71815AGW

I think the original idea was that Lee could get the Tag from Mark and
then get all the changes in via MFD tree. I can't say what would be the
best way to get these in. I'm open to all suggestions :)

Best Regards
	Matti Vaittinen