From: Mark Brown <broonie@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: lgirdwood@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, lee.jones@linaro.org
Subject: Re: [PATCH v3 RESEND 0/4] MediaTek Helio X10 MT6795 - MT6331/6332 Regulators
Date: Wed, 6 Jul 2022 14:52:55 +0100 [thread overview]
Message-ID: <YsWTt3YSHI9LLpnw@sirena.org.uk> (raw)
In-Reply-To: <82736173-b3b8-1e1a-3e2e-25d9ca3287eb@collabora.com>
[-- Attachment #1.1: Type: text/plain, Size: 1190 bytes --]
On Wed, Jul 06, 2022 at 03:38:34PM +0200, AngeloGioacchino Del Regno wrote:
> Il 06/07/22 14:57, Mark Brown ha scritto:
> > On Wed, Jul 06, 2022 at 02:49:56PM +0200, AngeloGioacchino Del Regno wrote:
> > > Il 06/07/22 14:16, Mark Brown ha scritto:
> >
> > > > This previously got 0day failures due to missing dependencies which
> > > > need would need a merge with IIRC MFD, I see no reference in the cover
> > > > letter to dependencies?
> >
> > > The only blocker for this series was the MFD patch, which got picked and
> > > it's present in next-20220706 (as you suggested me to resend when things
> > > were picked... I decided to wait until they actually landed on -next...)
> >
> > Right, I also said I'd need a pull request - if I apply the patches
> > without having the MFD bits they depend on in my tree then it will fail
> > to build.
>
> I remember writing that to Lee... how do we proceed in this case?
> Should we add him to the Cc's of this patch to notify him or..?
Lee, Angelo has sent me this series for Helio X10 which needs some MFD
bits (not 100% sure which, I guess Angelo can fill that in) - is there a
tagged branch available to pull in?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-06 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 10:09 [PATCH v3 RESEND 0/4] MediaTek Helio X10 MT6795 - MT6331/6332 Regulators AngeloGioacchino Del Regno
2022-07-06 10:09 ` [PATCH v3 RESEND 1/4] dt-bindings: regulator: Add bindings for MT6331 regulator AngeloGioacchino Del Regno
2022-07-06 10:09 ` [PATCH v3 RESEND 2/4] regulator: Add driver for MT6331 PMIC regulators AngeloGioacchino Del Regno
2022-07-06 10:09 ` [PATCH v3 RESEND 3/4] dt-bindings: regulator: Add bindings for MT6332 regulator AngeloGioacchino Del Regno
2022-07-06 10:09 ` [PATCH v3 RESEND 4/4] regulator: Add driver for MT6332 PMIC regulators AngeloGioacchino Del Regno
2022-07-06 12:16 ` [PATCH v3 RESEND 0/4] MediaTek Helio X10 MT6795 - MT6331/6332 Regulators Mark Brown
2022-07-06 12:49 ` AngeloGioacchino Del Regno
2022-07-06 12:57 ` Mark Brown
2022-07-06 13:38 ` AngeloGioacchino Del Regno
2022-07-06 13:52 ` Mark Brown [this message]
2022-07-06 13:59 ` AngeloGioacchino Del Regno
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=YsWTt3YSHI9LLpnw@sirena.org.uk \
--to=broonie@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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