From: kernel test robot <lkp@intel.com>
To: Ekansh Gupta <quic_ekangupt@quicinc.com>,
srinivas.kandagatla@linaro.org, linux-arm-msm@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Ekansh Gupta <quic_ekangupt@quicinc.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/5] misc: fastrpc: Add fastrpc multimode invoke request support
Date: Sun, 22 Oct 2023 06:29:33 +0800 [thread overview]
Message-ID: <202310220610.KdxUvBUu-lkp@intel.com> (raw)
In-Reply-To: <1697612560-9726-2-git-send-email-quic_ekangupt@quicinc.com>
Hi Ekansh,
kernel test robot noticed the following build errors:
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on char-misc/char-misc-next linus/master v6.6-rc6]
[cannot apply to char-misc/char-misc-linus next-20231020]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ekansh-Gupta/misc-fastrpc-Add-fastrpc-multimode-invoke-request-support/20231018-150423
base: char-misc/char-misc-testing
patch link: https://lore.kernel.org/r/1697612560-9726-2-git-send-email-quic_ekangupt%40quicinc.com
patch subject: [PATCH v5 1/5] misc: fastrpc: Add fastrpc multimode invoke request support
config: i386-randconfig-011-20231022 (https://download.01.org/0day-ci/archive/20231022/202310220610.KdxUvBUu-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231022/202310220610.KdxUvBUu-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/202310220610.KdxUvBUu-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from <command-line>:
>> ./usr/include/misc/fastrpc.h:89:33: error: C++ style comments are not allowed in ISO C90
89 | __u32 reserved[8]; // keeping reserved bits for new requirements
| ^
./usr/include/misc/fastrpc.h:89:33: note: (this will be reported only once per input file)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-21 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 7:02 [PATCH v5 0/5] Add multimode invoke request IOCTL support Ekansh Gupta
2023-10-18 7:02 ` [PATCH v5 1/5] misc: fastrpc: Add fastrpc multimode invoke request support Ekansh Gupta
2023-10-21 22:29 ` kernel test robot [this message]
2023-10-18 7:02 ` [PATCH v5 2/5] misc: fastrpc: Add CRC support for remote buffers Ekansh Gupta
2023-10-18 7:02 ` [PATCH v5 3/5] misc: fastrpc: Capture kernel and DSP performance counters Ekansh Gupta
2023-10-18 7:02 ` [PATCH v5 4/5] misc: fastrpc: Add support to save and restore interrupted Ekansh Gupta
2023-10-18 7:02 ` [PATCH v5 5/5] misc: fastrpc: Add support to allocate shared context bank Ekansh Gupta
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=202310220610.KdxUvBUu-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_ekangupt@quicinc.com \
--cc=srinivas.kandagatla@linaro.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