From: kernel test robot <lkp@intel.com>
To: Dawei Li <dawei.li@linux.dev>,
andersson@kernel.org, mathieu.poirier@linaro.org
Cc: oe-kbuild-all@lists.linux.dev, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org, dawei.li@linux.dev,
set_pte_at@outlook.com
Subject: Re: [PATCH 3/3] rpmsg: ctrl: Introduce RPMSG_CREATE_EPT_FD_IOCTL uAPI
Date: Fri, 9 May 2025 07:21:59 +0800 [thread overview]
Message-ID: <202505090716.iB4qQAf2-lkp@intel.com> (raw)
In-Reply-To: <20250507141712.4276-4-dawei.li@linux.dev>
Hi Dawei,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 92a09c47464d040866cf2b4cd052bc60555185fb]
url: https://github.com/intel-lab-lkp/linux/commits/Dawei-Li/rpmsg-char-Reuse-eptdev-logic-for-anon-device/20250507-223209
base: 92a09c47464d040866cf2b4cd052bc60555185fb
patch link: https://lore.kernel.org/r/20250507141712.4276-4-dawei.li%40linux.dev
patch subject: [PATCH 3/3] rpmsg: ctrl: Introduce RPMSG_CREATE_EPT_FD_IOCTL uAPI
config: i386-randconfig-011-20250508 (https://download.01.org/0day-ci/archive/20250509/202505090716.iB4qQAf2-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/20250509/202505090716.iB4qQAf2-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/202505090716.iB4qQAf2-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/rpmsg/rpmsg_ctrl.c:28:
drivers/rpmsg/rpmsg_char.h:54:1: error: expected identifier or '(' before '{' token
54 | {
| ^
>> drivers/rpmsg/rpmsg_char.h:52:19: warning: 'rpmsg_eptdev_create' used but never defined
52 | static inline int rpmsg_eptdev_create(struct rpmsg_device *rpdev, struct device *parent,
| ^~~~~~~~~~~~~~~~~~~
vim +/rpmsg_eptdev_create +52 drivers/rpmsg/rpmsg_char.h
69265bc12b6567 Arnaud Pouliquen 2022-01-24 51
73c9f094eaac8b Dawei Li 2025-05-07 @52 static inline int rpmsg_eptdev_create(struct rpmsg_device *rpdev, struct device *parent,
73c9f094eaac8b Dawei Li 2025-05-07 53 struct rpmsg_channel_info chinfo, int *pfd);
73c9f094eaac8b Dawei Li 2025-05-07 @54 {
73c9f094eaac8b Dawei Li 2025-05-07 55 return -ENXIO;
73c9f094eaac8b Dawei Li 2025-05-07 56 }
73c9f094eaac8b Dawei Li 2025-05-07 57
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-05-08 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 14:17 [PATCH 0/3] rpmsg: Introduce RPMSG_CREATE_EPT_FD_IOCTL uAPI Dawei Li
2025-05-07 14:17 ` [PATCH 1/3] rpmsg: char: Reuse eptdev logic for anon device Dawei Li
2025-05-07 14:17 ` [PATCH 2/3] rpmsg: char: Implement eptdev based on anon inode Dawei Li
2025-05-08 18:37 ` kernel test robot
2025-05-07 14:17 ` [PATCH 3/3] rpmsg: ctrl: Introduce RPMSG_CREATE_EPT_FD_IOCTL uAPI Dawei Li
2025-05-08 23:21 ` kernel test robot [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=202505090716.iB4qQAf2-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=dawei.li@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=set_pte_at@outlook.com \
/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