From: Geert Uytterhoeven <geert@linux-m68k.org>
To: kbuild test robot <lkp@intel.com>
Cc: "Geert Uytterhoeven" <geert+renesas@glider.be>,
kbuild-all@lists.01.org,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: Re: [renesas-drivers:sh-pfc-for-v5.7 13/13] drivers/pinctrl/sh-pfc/core.c:1037:1: error: expected identifier or '(' before '}' token
Date: Mon, 10 Feb 2020 19:47:22 +0100 [thread overview]
Message-ID: <CAMuHMdWPG7=vEBFWXQ6TJ4SEXbFAn-0JcpLq2EeseX+82nPuHw@mail.gmail.com> (raw)
In-Reply-To: <202002110233.bPq1aJyL%lkp@intel.com>
On Mon, Feb 10, 2020 at 7:27 PM kbuild test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git sh-pfc-for-v5.7
> head: 143a21c22d849a243c899408c1cf8bd8bdcd72cd
> commit: 143a21c22d849a243c899408c1cf8bd8bdcd72cd [13/13] pinctrl: sh-pfc: checker: Add function GPIO checks
> config: i386-allyesconfig (attached as .config)
> compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
> reproduce:
> git checkout 143a21c22d849a243c899408c1cf8bd8bdcd72cd
> # save the attached .config to linux build tree
> make ARCH=i386
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> >> drivers/pinctrl/sh-pfc/core.c:1037:1: error: expected identifier or '(' before '}' token
> }
> ^
Thanks, bad fixup. Fixed.
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
prev parent reply other threads:[~2020-02-10 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 18:25 [renesas-drivers:sh-pfc-for-v5.7 13/13] drivers/pinctrl/sh-pfc/core.c:1037:1: error: expected identifier or '(' before '}' token kbuild test robot
2020-02-10 18:47 ` Geert Uytterhoeven [this message]
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='CAMuHMdWPG7=vEBFWXQ6TJ4SEXbFAn-0JcpLq2EeseX+82nPuHw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=geert+renesas@glider.be \
--cc=kbuild-all@lists.01.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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;
as well as URLs for NNTP newsgroup(s).