Re: [PATCH v8 00/10] Support ROHM BD99954 charger IC

From: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
To: "broonie@kernel.org" <broonie@kernel.org>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
	"andrei.stefanescu@microchip.com"
	<andrei.stefanescu@microchip.com>,
	"heiko@sntech.de" <heiko@sntech.de>,
	"rafael@kernel.org" <rafael@kernel.org>,
	"tony@atomide.com" <tony@atomide.com>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"brendanhiggins@google.com" <brendanhiggins@google.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"kholk11@gmail.com" <kholk11@gmail.com>,
	"hsin-hsiung.wang@mediatek.com" <hsin-hsiung.wang@mediatek.com>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	"axel.lin@ingics.com" <axel.lin@ingics.com>,
	"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
	"b.zolnierkie@samsung.com" <b.zolnierkie@samsung.com>,
	"krzk@kernel.org" <krzk@kernel.org>,
	"m.reichl@fivetechno.de" <m.reichl@fivetechno.de>,
	"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
	"wens@csie.org" <wens@csie.org>,
	"andreas@kemnade.info" <andreas@kemnade.info>,
	"agross@kernel.org" <agross@kernel.org>,
	"Laine, Markus" <Markus.Laine@fi.rohmeurope.com>,
	"Adam.Thomson.Opensource@diasemi.com"
	<Adam.Thomson.Opensource@diasemi.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"ckeepax@opensource.cirrus.com" <ckeepax@opensource.cirrus.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"rf@opensource.cirrus.com" <rf@opensource.cirrus.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"sre@kernel.org" <sre@kernel.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"andriy.shevchenko@linux.intel.com"
	<andriy.shevchenko@linux.intel.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"support.opensource@diasemi.com" <support.opensource@diasemi.com>,
	"baolin.wang@linaro.org" <baolin.wang@linaro.org>,
	"Mutanen,  Mikko" <Mikko.Mutanen@fi.rohmeurope.com>,
	"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
	"rdunlap@infradead.org" <rdunlap@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"sbkim73@samsung.com" <sbkim73@samsung.com>,
	"vkoul@kernel.org" <vkoul@kernel.org>,
	"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"mazziesaccount@gmail.com" <mazziesaccount@gmail.com>
Subject: Re: [PATCH v8 00/10] Support ROHM BD99954 charger IC
Date: Fri, 3 Apr 2020 12:30:17 +0000	[thread overview]
Message-ID: <c149a7b377e4e4a26fffa8c9413f3854223985e9.camel@fi.rohmeurope.com> (raw)
In-Reply-To: <20200403120135.GE4286@sirena.org.uk>

On Fri, 2020-04-03 at 13:01 +0100, Mark Brown wrote:
> On Fri, Apr 03, 2020 at 11:13:54AM +0000, Vaittinen, Matti wrote:
> > On Fri, 2020-04-03 at 14:02 +0300, 
> > andriy.shevchenko@linux.intel.com
> > > From my point of view, you need to wait till rc1 is out and
> > > rebase
> > > the series.
> > > The cross-subsystem changes can be handled by maintainers in a
> > > form
> > > of
> > > immutable branches / tags. On your side you may recommend them
> > > how to
> > > proceed,
> > > but the final decision is by them.
> > Thanks Andy. I re-read what I wrote and I see it can be interpreted
> > as
> > if I was trying to tell how things should be done. That was my
> > intention. My intention was to point out that my patches will break
> > regulator tree builds if new drivers are added.
> > > From my point of view, you need to wait till rc1 is out and
> > > rebase
> > > the series.
> > Does this mean that there is no new regulator drivers expected to
> > be
> > added after rc1 is out? If this is the case, the rebasing this
> > series
> > on top of rc1 should work as then I get all new drivers (for a
> > release)
> 
> During the merge window no new anything except bug fixes is expected
> to
> be applied.  Like Andy says we'll share a branch for any
> dependencies,
> nobody in particular seems to apply code for lib so I guess I'll take
> that patch and the regulator one and share it but not until after the
> merge window.

Thanks for taking it Mark. So I should rebase and resend when v5.7-rc1
is tagged as Andy suggested? 

--Matti

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek