From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Phil Edworthy <phil.edworthy@renesas.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the pinctrl-renesas tree
Date: Thu, 30 Jun 2022 15:15:11 +1000 [thread overview]
Message-ID: <20220630151511.58281e52@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Hi all,
After merging the pinctrl-renesas tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/pinctrl/renesas/pinctrl-rzv2m.c: In function 'rzv2m_dt_subnode_to_map':
drivers/pinctrl/renesas/pinctrl-rzv2m.c:37:33: error: implicit declaration of function 'FIELD_GET' [-Werror=implicit-function-declaration]
37 | #define MUX_FUNC(pinconf) FIELD_GET(MUX_FUNC_MASK, (pinconf))
| ^~~~~~~~~
drivers/pinctrl/renesas/pinctrl-rzv2m.c:306:31: note: in expansion of macro 'MUX_FUNC'
306 | psel_val[i] = MUX_FUNC(value);
| ^~~~~~~~
cc1: all warnings being treated as errors
Caused by commit
1e18476c392f ("pinctrl: renesas: Add RZ/V2M pin and gpio controller driver")
I have used the pinctrl-renesas tree from next-20220629 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-06-30 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 5:15 Stephen Rothwell [this message]
2022-06-30 9:25 ` linux-next: build failure after merge of the pinctrl-renesas tree Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2022-04-20 4:55 Stephen Rothwell
2022-04-20 9:58 ` Geert Uytterhoeven
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=20220630151511.58281e52@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=phil.edworthy@renesas.com \
/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