From: kernel test robot <lkp@intel.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [sudeep-holla:v6.7/ffa_integ_test 5/5] drivers/firmware/arm_ffa/test_driver.c:28:6: warning: no previous prototype for 'test_ffa_notif_cb'
Date: Fri, 10 Nov 2023 02:49:15 +0800 [thread overview]
Message-ID: <202311100209.nmATysYA-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git v6.7/ffa_integ_test
head: 0dfce5abe57576c4804fc626172b0cd80a320c1c
commit: 0dfce5abe57576c4804fc626172b0cd80a320c1c [5/5] firmware: arm_ffa: Add test driver
config: arm64-randconfig-001-20231110 (https://download.01.org/0day-ci/archive/20231110/202311100209.nmATysYA-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231110/202311100209.nmATysYA-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/202311100209.nmATysYA-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/firmware/arm_ffa/test_driver.c:28:6: warning: no previous prototype for 'test_ffa_notif_cb' [-Wmissing-prototypes]
28 | void test_ffa_notif_cb(int notification_id, void *data)
| ^~~~~~~~~~~~~~~~~
vim +/test_ffa_notif_cb +28 drivers/firmware/arm_ffa/test_driver.c
26
27
> 28 void test_ffa_notif_cb(int notification_id, void *data)
29 {
30 pr_info("%x %p\n", notification_id, data);
31 }
32
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-09 18:49 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=202311100209.nmATysYA-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.