From: Rob Herring <robh@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: [linux-next:master 3825/5027] arch/mips/pic32/pic32mzda/config.c:22:8: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int
Date: Thu, 27 Jul 2023 12:56:10 -0600 [thread overview]
Message-ID: <CAL_JsqKGgt18rPaE1JsVZGru6Y-gwyf3t94gL+Knpt21QRW6sQ@mail.gmail.com> (raw)
In-Reply-To: <202307280212.w1lY1gCG-lkp@intel.com>
On Thu, Jul 27, 2023 at 12:19 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 451cc82bd11eb6a374f4dbcfc1cf007eafea91ab
> commit: 657c45b303f87d77eb4ef49e9452f1c5d1fc363c [3825/5027] MIPS: Explicitly include correct DT includes
> config: mips-randconfig-r022-20230727 (https://download.01.org/0day-ci/archive/20230728/202307280212.w1lY1gCG-lkp@intel.com/config)
> compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
> reproduce: (https://download.01.org/0day-ci/archive/20230728/202307280212.w1lY1gCG-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202307280212.w1lY1gCG-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> arch/mips/pic32/pic32mzda/config.c:22:8: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
> 22 | static DEFINE_SPINLOCK(config_lock);
> | ~~~~~~ ^
> | int
> >> arch/mips/pic32/pic32mzda/config.c:22:24: error: a parameter list without types is only allowed in a function definition
> 22 | static DEFINE_SPINLOCK(config_lock);
> | ^
> >> arch/mips/pic32/pic32mzda/config.c:41:2: error: call to undeclared function 'spin_lock_irqsave'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> 41 | spin_lock_irqsave(&config_lock, flags);
> | ^
> >> arch/mips/pic32/pic32mzda/config.c:41:21: error: use of undeclared identifier 'config_lock'
> 41 | spin_lock_irqsave(&config_lock, flags);
> | ^
> >> arch/mips/pic32/pic32mzda/config.c:46:2: error: call to undeclared function 'spin_unlock_irqrestore'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> 46 | spin_unlock_irqrestore(&config_lock, flags);
> | ^
> arch/mips/pic32/pic32mzda/config.c:46:26: error: use of undeclared identifier 'config_lock'
> 46 | spin_unlock_irqrestore(&config_lock, flags);
> | ^
> 6 errors generated.
Already fixed in [1].
Rob
[1] https://lore.kernel.org/all/20230727012028.3933785-1-robh@kernel.org/
prev parent reply other threads:[~2023-07-27 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 18:18 kernel test robot
2023-07-27 18:56 ` Rob Herring [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=CAL_JsqKGgt18rPaE1JsVZGru6Y-gwyf3t94gL+Knpt21QRW6sQ@mail.gmail.com \
--to=robh@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tsbogend@alpha.franken.de \
/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