All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: build failure after merge of the pinctrl-renesas tree
Date: Thu, 30 Jun 2022 11:25:03 +0200	[thread overview]
Message-ID: <CAMuHMdVD0XZg5grY251D4tqxmJ6bH4MWK2s_4+yLRBdUzPBLTg@mail.gmail.com> (raw)
In-Reply-To: <20220630151511.58281e52@canb.auug.org.au>

Hi Stephen,

On Thu, Jun 30, 2022 at 7:15 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 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.

Thanks for the report.  This was missing an include of <linux/bitfield.h>,
which is included implicitly on arm64.

Fixed and updated.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2022-06-30  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30  5:15 linux-next: build failure after merge of the pinctrl-renesas tree Stephen Rothwell
2022-06-30  9:25 ` Geert Uytterhoeven [this message]
  -- 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=CAMuHMdVD0XZg5grY251D4tqxmJ6bH4MWK2s_4+yLRBdUzPBLTg@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=phil.edworthy@renesas.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.