From: Mark Brown <broonie@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: kernel test robot <lkp@intel.com>,
lgirdwood@gmail.com, llvm@lists.linux.dev,
kbuild-all@lists.01.org, 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
Subject: Re: [PATCH v3 4/4] regulator: Add driver for MT6332 PMIC regulators
Date: Mon, 30 May 2022 16:25:50 +0200 [thread overview]
Message-ID: <YpTT7l0oAJ51Df5A@sirena.org.uk> (raw)
In-Reply-To: <540be3e8-6a97-5e80-3767-892025ded07b@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
On Mon, May 30, 2022 at 11:33:28AM +0200, AngeloGioacchino Del Regno wrote:
> Il 26/05/22 17:12, kernel test robot ha scritto:
> > > > drivers/regulator/mt6332-regulator.c:15:10: fatal error: 'linux/mfd/mt6332/registers.h' file not found
> > #include <linux/mfd/mt6332/registers.h>
> Note for maintainers: this failure is expected, as this series depends on the
> series that introduces the MT6331 and MT6332 MFD device (with its headers, used
> by the regulator driver of this series)
> https://patchwork.kernel.org/project/linux-mediatek/list/?series=643602
That's
mfd: mt6397: Add basic support for MT6331+MT6332 PMIC
It looks like that's not yet been applied - please resubmit when
that series has been applied. I'll need a pull request for the
MFD bits I guess, please make sure Lee knows that's going to be
needed.
Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-05-30 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 15:47 [PATCH v3 0/4] MediaTek Helio X10 MT6795 - MT6331/6332 Regulators AngeloGioacchino Del Regno
2022-05-23 15:47 ` [PATCH v3 1/4] dt-bindings: regulator: Add bindings for MT6331 regulator AngeloGioacchino Del Regno
2022-05-24 9:56 ` Krzysztof Kozlowski
2022-05-23 15:47 ` [PATCH v3 2/4] regulator: Add driver for MT6331 PMIC regulators AngeloGioacchino Del Regno
2022-05-26 12:08 ` kernel test robot
2022-05-23 15:47 ` [PATCH v3 3/4] dt-bindings: regulator: Add bindings for MT6332 regulator AngeloGioacchino Del Regno
2022-05-24 9:56 ` Krzysztof Kozlowski
2022-05-23 15:47 ` [PATCH v3 4/4] regulator: Add driver for MT6332 PMIC regulators AngeloGioacchino Del Regno
2022-05-26 15:12 ` kernel test robot
2022-05-30 9:33 ` AngeloGioacchino Del Regno
2022-05-30 14:25 ` Mark Brown [this message]
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=YpTT7l0oAJ51Df5A@sirena.org.uk \
--to=broonie@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=krzysztof.kozlowski+dt@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=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).