From: kernel test robot <lkp@intel.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 6093/6126] include/linux/usb/typec_mux.h:77:1: error: expected identifier or '(' before '{' token
Date: Wed, 31 May 2023 17:10:07 +0800 [thread overview]
Message-ID: <202305311652.OP9x8xkW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: d4cee89031c80066ec461bb77b5e13a4f37d5fd2
commit: 8bf3c33a5ebf4f4faab2bafb1d237f3051ae2499 [6093/6126] Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git
config: parisc-randconfig-r025-20230531 (https://download.01.org/0day-ci/archive/20230531/202305311652.OP9x8xkW-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 12.3.0
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8bf3c33a5ebf4f4faab2bafb1d237f3051ae2499
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 8bf3c33a5ebf4f4faab2bafb1d237f3051ae2499
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=parisc olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash drivers/phy/qualcomm/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202305311652.OP9x8xkW-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/phy/qualcomm/phy-qcom-qmp-combo.c:23:
>> include/linux/usb/typec_mux.h:77:1: error: expected identifier or '(' before '{' token
77 | {
| ^
include/linux/usb/typec_mux.h:76:33: warning: 'fwnode_typec_mux_get' used but never defined
76 | static inline struct typec_mux *fwnode_typec_mux_get(struct fwnode_handle *fwnode);
| ^~~~~~~~~~~~~~~~~~~~
vim +77 include/linux/usb/typec_mux.h
a37599ebfb656c Prashant Malani 2022-06-15 75
3524fe31538c1a Heikki Krogerus 2023-05-26 76 static inline struct typec_mux *fwnode_typec_mux_get(struct fwnode_handle *fwnode);
a37599ebfb656c Prashant Malani 2022-06-15 @77 {
a37599ebfb656c Prashant Malani 2022-06-15 78 return NULL;
a37599ebfb656c Prashant Malani 2022-06-15 79 }
a37599ebfb656c Prashant Malani 2022-06-15 80
:::::: The code at line 77 was first introduced by commit
:::::: a37599ebfb656c2af4ca119de556eba29b6926d6 usb: typec: mux: Add CONFIG guards for functions
:::::: TO: Prashant Malani <pmalani@chromium.org>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-05-31 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:10 kernel test robot [this message]
2023-05-31 18:52 [linux-next:master 6093/6126] include/linux/usb/typec_mux.h:77:1: error: expected identifier or '(' before '{' token kernel test robot
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=202305311652.OP9x8xkW-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vkoul@kernel.org \
/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).