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")
I have used the regulator tree from next-20211021 for today.
--
Cheers,
Stephen Rothwell
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
>
On Fri, Oct 22, 2021 at 08:31:08PM +1000, Alistair wrote:
> 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.
Let's just add the dependency back until the MFD gets sorted out :/