From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: "mazziesaccount@gmail.com" <mazziesaccount@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"sre@kernel.org" <sre@kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"a.zummo@towertech.it" <a.zummo@towertech.it>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"Mutanen, Mikko" <Mikko.Mutanen@fi.rohmeurope.com>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
"wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"Haikola, Heikki" <Heikki.Haikola@fi.rohmeurope.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v14 0/8] support ROHM BD70528 PMIC
Date: Tue, 21 May 2019 13:41:49 +0200 [thread overview]
Message-ID: <20190521114149.GG3274@piout.net> (raw)
In-Reply-To: <3a78cc77499d5027f527be51a7c40f6c5d70338c.camel@fi.rohmeurope.com>
On 21/05/2019 11:01:53+0000, Vaittinen, Matti wrote:
> Hello All,
>
> On Thu, 2019-05-02 at 12:11 +0300, Matti Vaittinen wrote:
> > Patch series introducing support for ROHM BD70528 PMIC
> >
> Just thought I'd ask if there's any chances to get this series in 5.2?
> It seems to me the WDT part (patch 8) was already merged in but rest of
> the patches seem to be in limbo somewhere :)
>
> I guess most of the patches have relevant acks - so wonder if the rest
> can go through Lee's tree? I admit I am getting slightly impatient -
> sorry for that :]
>
Nope, the 5.2 merge windows is closed. This will have to wait for 5.3.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-21 11:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 9:11 [PATCH v14 0/8] support ROHM BD70528 PMIC Matti Vaittinen
2019-05-02 9:12 ` [PATCH v14 1/8] mfd: regulator: clk: split rohm-bd718x7.h Matti Vaittinen
2019-05-02 9:13 ` [PATCH v14 2/8] mfd: bd70528: Support ROHM bd70528 PMIC - core Matti Vaittinen
2019-05-08 11:24 ` Lee Jones
2019-05-02 9:13 ` [PATCH v14 3/8] clk: bd718x7: Support ROHM BD70528 clk block Matti Vaittinen
2019-05-02 9:14 ` [PATCH v14 4/8] dt-bindings: mfd: Document first ROHM BD70528 bindings Matti Vaittinen
2019-05-08 11:25 ` Lee Jones
2019-05-02 9:15 ` [PATCH v14 5/8] gpio: Initial support for ROHM bd70528 GPIO block Matti Vaittinen
2019-05-02 9:15 ` [PATCH v14 6/8] rtc: bd70528: Initial support for ROHM bd70528 RTC Matti Vaittinen
2019-05-02 9:17 ` [PATCH v14 7/8] power: supply: Initial support for ROHM BD70528 PMIC charger block Matti Vaittinen
2019-05-02 19:50 ` Sebastian Reichel
2019-05-03 5:29 ` Vaittinen, Matti
2019-05-02 9:17 ` [PATCH v14 8/8] watchdog: bd70528: Initial support for ROHM BD70528 watchdog block Matti Vaittinen
2019-05-21 11:01 ` [PATCH v14 0/8] support ROHM BD70528 PMIC Vaittinen, Matti
2019-05-21 11:41 ` Alexandre Belloni [this message]
2019-05-21 12:24 ` Vaittinen, Matti
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=20190521114149.GG3274@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=Heikki.Haikola@fi.rohmeurope.com \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=Mikko.Mutanen@fi.rohmeurope.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=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 \
--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).