Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
User-Agent: Cyrus-JMAP/3.5.0-alpha0-1369-gd055fb5e7c-fm-20211018.002-gd055fb5e
Mime-Version: 1.0
Message-Id: <bd49c44d-372e-453a-ac8e-04252b2eaba8@www.fastmail.com>
In-Reply-To: <20211022125323.132b950d@canb.auug.org.au>
References: <20211022125323.132b950d@canb.auug.org.au>
Date:   Fri, 22 Oct 2021 20:31:08 +1000
From:   Alistair <alistair@alistair23.me>
To:     "Stephen Rothwell" <sfr@canb.auug.org.au>,
        "Mark Brown" <broonie@kernel.org>,
        "Liam Girdwood" <lgirdwood@gmail.com>
Cc:     "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
        "Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the regulator tree
Content-Type: text/plain
Precedence: bulk

On Fri, Oct 22, 2021, at 11:53 AM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the regulator tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/regulator/sy7636a-regulator.c:14:10: fatal error: linux/mfd/sy7636a.h: No such file or directory
>    14 | #include <linux/mfd/sy7636a.h>
>       |          ^~~~~~~~~~~~~~~~~~~~~
> 
> Caused by commit
> 
>   cb17820ef71e ("regulator: sy7636a: Remove requirement on sy7636a mfd")

The above patch allows the sy7636a regulator to be built, as it no longer depends on
the mfd driver directly.
This fails to build on current upstream as the sy7636a header file isn't upstream
yet. The header file is added earlier in the patch series.

This patch should probably not be applied until after:

mfd: simple-mfd-i2c: Enable support for the silergy,sy7636a

Or if preferred I can split adding the header file into it's own patch that can be
applied.

Alistair


> 
> I have used the regulator tree from next-20211021 for today.
> 
> -- 
> Cheers,
> Stephen Rothwell
>