From: kernel test robot <lkp@intel.com>
To: Marc Bonnici <marc.bonnici@arm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>
Subject: [sudeep-holla:ffa_notifications_proto 4/15] drivers/firmware/arm_ffa/driver.c:725:6: warning: no previous prototype for '__enable_schedule_receiver_interrupt'
Date: Tue, 26 Oct 2021 09:16:33 +0800 [thread overview]
Message-ID: <202110260929.hDI3zDnA-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2883 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git ffa_notifications_proto
head: c58dfd7efd456c261212967aebc7938a7d5998be
commit: f2d94829406ec4bbbab8ed6ac13d0ff25280ff37 [4/15] ffa_driver: Initial support for Scheduler Receiver Interrupt
config: arm64-randconfig-r023-20211021 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
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/sudeep.holla/linux.git/commit/?id=f2d94829406ec4bbbab8ed6ac13d0ff25280ff37
git remote add sudeep-holla https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git
git fetch --no-tags sudeep-holla ffa_notifications_proto
git checkout f2d94829406ec4bbbab8ed6ac13d0ff25280ff37
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/firmware/arm_ffa/driver.c: In function 'ffa_compatible_version_find':
drivers/firmware/arm_ffa/driver.c:193:13: warning: unused variable 'compat_version' [-Wunused-variable]
193 | u32 compat_version;
| ^~~~~~~~~~~~~~
drivers/firmware/arm_ffa/driver.c: At top level:
>> drivers/firmware/arm_ffa/driver.c:725:6: warning: no previous prototype for '__enable_schedule_receiver_interrupt' [-Wmissing-prototypes]
725 | void __enable_schedule_receiver_interrupt(void* _) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
>> drivers/firmware/arm_ffa/driver.c:716: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Handle an SGI
drivers/firmware/arm_ffa/driver.c:732: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Registers for the notification avaliable interrupt.
vim +/__enable_schedule_receiver_interrupt +725 drivers/firmware/arm_ffa/driver.c
713
714
715 /**
> 716 * Handle an SGI
717 */
718 static irqreturn_t irq_handler(int irq, void *dev)
719 {
720 return IRQ_HANDLED;
721 }
722
723
724 /* Helper function to register on all CPUS. */
> 725 void __enable_schedule_receiver_interrupt(void* _) {
726 enable_percpu_irq(ffa_sched_recv_int_id, IRQ_TYPE_EDGE_RISING);
727 pr_info("Enabled Scheduler Receiver IRQ %d on cpu: %d\n",
728 ffa_sched_recv_int_id, smp_processor_id());
729 }
730
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 47178 bytes --]
reply other threads:[~2021-10-26 1:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202110260929.hDI3zDnA-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.bonnici@arm.com \
--cc=sudeep.holla@arm.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