[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82736173-b3b8-1e1a-3e2e-25d9ca3287eb@collabora.com>
Date: Wed, 6 Jul 2022 15:38:34 +0200
From: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
To: Mark Brown <broonie@...nel.org>
Cc: lgirdwood@...il.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, matthias.bgg@...il.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v3 RESEND 0/4] MediaTek Helio X10 MT6795 - MT6331/6332
Regulators
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..?
P.S.: Sorry, this is the first time that I deal with MFD...
Powered by blists - more mailing lists