[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231114131335.3aba4f4d@canb.auug.org.au>
Date: Tue, 14 Nov 2023 13:13:35 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: build failure after merge of the pinctrl tree
Hi all,
After merging the pinctrl tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/pinctrl/qcom/pinctrl-sm8650-lpass-lpi.c:232:10: error: 'const struct lpi_pinctrl_variant_data' has no member named 'flags'
232 | .flags = LPI_FLAG_SLEW_RATE_SAME_REG,
| ^~~~~
drivers/pinctrl/qcom/pinctrl-sm8650-lpass-lpi.c:232:18: error: 'LPI_FLAG_SLEW_RATE_SAME_REG' undeclared here (not in a function); did you mean 'LPI_SLEW_RATE_CTL_REG'?
232 | .flags = LPI_FLAG_SLEW_RATE_SAME_REG,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
| LPI_SLEW_RATE_CTL_REG
drivers/pinctrl/qcom/pinctrl-sm8650-lpass-lpi.c:232:18: error: excess elements in struct initializer [-Werror]
drivers/pinctrl/qcom/pinctrl-sm8650-lpass-lpi.c:232:18: note: (near initialization for 'sm8650_lpi_data')
cc1: all warnings being treated as errors
Caused by commit
c4e47673853f ("pinctrl: qcom: sm8650-lpass-lpi: add SM8650 LPASS")
I have used the pinctrl tree from next-20231113 for today.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists