From: Mark Brown <broonie@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Gene Chen <gene.chen.richtek@gmail.com>,
matthias.bgg@gmail.com, matti.vaittinen@fi.rohmeurope.com,
robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org, gene_chen@richtek.com,
Wilma.Wu@mediatek.com, cy_huang@richtek.com,
benjamin.chao@mediatek.com
Subject: Re: [PATCH resend v6 0/3] power: supply: mt6360_charger: add MT6360 charger support
Date: Fri, 13 Aug 2021 17:32:54 +0100 [thread overview]
Message-ID: <20210813163254.GF5209@sirena.org.uk> (raw)
In-Reply-To: <20210813162029.q5slrkubelfy3mvh@earth.universe>
[-- Attachment #1.1: Type: text/plain, Size: 837 bytes --]
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.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2021-08-13 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 3:39 [PATCH resend v6 0/3] power: supply: mt6360_charger: add MT6360 charger support Gene Chen
2021-07-19 3:39 ` [PATCH resend v6 1/3] lib: add linear range get selector within Gene Chen
2021-07-19 3:39 ` [PATCH resend v6 2/3] dt-bindings: power: Add bindings document for Charger support on MT6360 PMIC Gene Chen
2021-07-19 3:39 ` [PATCH resend v6 3/3] power: supply: mt6360_charger: add MT6360 charger support Gene Chen
2021-08-13 15:54 ` [PATCH resend v6 0/3] " Sebastian Reichel
2021-08-13 15:58 ` Mark Brown
2021-08-13 16:20 ` Sebastian Reichel
2021-08-13 16:32 ` Mark Brown [this message]
2021-08-13 17:11 ` Sebastian Reichel
2021-08-13 17:25 ` Mark Brown
2021-08-16 5:12 ` 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=20210813163254.GF5209@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Wilma.Wu@mediatek.com \
--cc=benjamin.chao@mediatek.com \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=gene.chen.richtek@gmail.com \
--cc=gene_chen@richtek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.com \
/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).