[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210813163254.GF5209@sirena.org.uk>
Date: Fri, 13 Aug 2021 17:32:54 +0100
From: Mark Brown <broonie@...nel.org>
To: Sebastian Reichel <sebastian.reichel@...labora.com>
Cc: Gene Chen <gene.chen.richtek@...il.com>, matthias.bgg@...il.com,
matti.vaittinen@...rohmeurope.com, robh+dt@...nel.org,
devicetree@...r.kernel.org, linux-pm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
rdunlap@...radead.org, gene_chen@...htek.com,
Wilma.Wu@...iatek.com, cy_huang@...htek.com,
benjamin.chao@...iatek.com
Subject: Re: [PATCH resend v6 0/3] power: supply: mt6360_charger: add MT6360
charger support
On Fri, Aug 13, 2021 at 06:20:29PM +0200, Sebastian Reichel wrote:
> On Fri, Aug 13, 2021 at 04:58:58PM +0100, Mark Brown wrote:
> > We're still waiting for review from Matti on the linear ranges bit -
> > normally that goes through the regulator tree, do you have a tag to pull
> > in case of merge conflicts?
> He actually already provided his Rb in v5, Gene did not carry it
> over properly (I added it) and the patch looks simple enough, that
> Linus will know what to do in case of a conflict. But if you insist
> I can unroll my tree and create a topic branch for this.
It would be better, the issues I'm worrying about are more general
refactorings or whatever that create actual dependencies rather than
just trivial add/add type issues - it can make doing some kinds of work
really painful if things go via a different tree.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists