From: kernel test robot <[email protected]>
To: Quentin Perret <[email protected]>
Cc: [email protected],
GNU/Weeb Mailing List <[email protected]>,
[email protected]
Subject: [ammarfaizi2-block:google/android/kernel/common/android12-5.10-2022-02 1555/9999] kernel/tracepoint.c:720:5: warning: no previous prototype for 'android_rvh_probe_register'
Date: Wed, 16 Mar 2022 17:09:50 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Quentin,
FYI, the error/warning still remains.
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android12-5.10-2022-02
head: 32c0a362f1a90ddf603ecd83a47a5b8e2b7a12fb
commit: cc6eed90a467a413b9c62fdd76e8f06347266a88 [1555/9999] ANDROID: vendor_hooks: Allow multiple attachments to restricted hooks
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220316/[email protected]/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce (this is a W=1 build):
# https://github.com/ammarfaizi2/linux-block/commit/cc6eed90a467a413b9c62fdd76e8f06347266a88
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android12-5.10-2022-02
git checkout cc6eed90a467a413b9c62fdd76e8f06347266a88
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <[email protected]>
All warnings (new ones prefixed by >>):
>> kernel/tracepoint.c:720:5: warning: no previous prototype for 'android_rvh_probe_register' [-Wmissing-prototypes]
720 | int android_rvh_probe_register(struct tracepoint *tp, void *probe, void *data)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/android_rvh_probe_register +720 kernel/tracepoint.c
719
> 720 int android_rvh_probe_register(struct tracepoint *tp, void *probe, void *data)
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/[email protected]
reply other threads:[~2022-03-16 9:10 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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