From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>,
mazziesaccount@gmail.com, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
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
Subject: Re: [PATCH v15 0/7] support ROHM BD70528 PMIC
Date: Wed, 19 Jun 2019 16:31:12 +0200 [thread overview]
Message-ID: <20190619143112.GO23549@piout.net> (raw)
In-Reply-To: <20190613130529.kgswgbuszb24itxz@earth.universe>
On 13/06/2019 15:05:29+0200, Sebastian Reichel wrote:
> Hi,
>
> On Wed, Jun 12, 2019 at 07:03:28AM +0100, Lee Jones wrote:
> > On Tue, 11 Jun 2019, Sebastian Reichel wrote:
> > > On Mon, Jun 03, 2019 at 10:23:37AM +0300, Matti Vaittinen wrote:
> > > > Patch series introducing support for ROHM BD70528 PMIC
> > > > [...]
> > >
> > > I think all patches have been reviewed by the respective subsystem
> > > maintainers. Lee, can you provide an immutable branch with the MFD
> > > patches (1, 2, 4)? Looks like the other patches only depend on those
> > > and can go through their respective subsystems.
> >
> > Yes. It's on my TODO list.
>
> Thanks.
>
> > Would you prefer this method over me just taking them all and sending
> > out a PR? The latter is my usual flow, but I'm happy with either.
>
> Both methods are fine with me. I usually go with "my" method, since
> that results in less shared commits. It simplifies potential
> follow-up bug fixes, since there is only one tree to fix.
>
Personally, I'm fine with Lee taking everything in his tree as it is
very unlikely to require follow up patches this cycle (i.e before rc1).
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-19 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 7:23 [PATCH v15 0/7] support ROHM BD70528 PMIC Matti Vaittinen
2019-06-03 7:24 ` [PATCH v15 1/7] mfd: regulator: clk: split rohm-bd718x7.h Matti Vaittinen
2019-06-03 7:25 ` [PATCH v15 2/7] mfd: bd70528: Support ROHM bd70528 PMIC - core Matti Vaittinen
2019-06-03 7:25 ` [PATCH v15 3/7] clk: bd718x7: Support ROHM BD70528 clk block Matti Vaittinen
2019-06-03 7:26 ` [PATCH v15 4/7] dt-bindings: mfd: Document first ROHM BD70528 bindings Matti Vaittinen
2019-06-03 7:26 ` [PATCH v15 5/7] gpio: Initial support for ROHM bd70528 GPIO block Matti Vaittinen
2019-06-03 7:27 ` [PATCH v15 6/7] rtc: bd70528: Initial support for ROHM bd70528 RTC Matti Vaittinen
2019-06-03 7:28 ` [PATCH v15 7/7] power: supply: Initial support for ROHM BD70528 PMIC charger block Matti Vaittinen
2019-06-11 20:00 ` [PATCH v15 0/7] support ROHM BD70528 PMIC Sebastian Reichel
2019-06-12 6:03 ` Lee Jones
2019-06-13 8:35 ` Matti Vaittinen
2019-06-13 13:05 ` Sebastian Reichel
2019-06-19 14:31 ` Alexandre Belloni [this message]
2019-06-27 13:30 ` [GIT PULL] Immutable branch between MFD, Clk, GPIO, Power, Regulator and RTC due for the v5.3 merge window Lee Jones
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=20190619143112.GO23549@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=mark.rutland@arm.com \
--cc=mazziesaccount@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sre@kernel.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).