From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 2/2] drivers/base/power/wakeup.c:1219:5: warning: no previous prototype for 'wakeup_sources_stats_open'
Date: Sun, 25 Oct 2026 01:32:03 +0800 [thread overview]
Message-ID: <202610250109.I5tYNwcI-lkp@intel.com> (raw)
Hi Bo,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12
head: 32521e28daaacb02caff14090988d91503e61978
commit: 5df128deb8f2e04a46acb77df6aec44b1d343583 [2/2] ANDROID: Allow vendor modules to get wakeup sources data.
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20261025/202610250109.I5tYNwcI-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261025/202610250109.I5tYNwcI-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/202610250109.I5tYNwcI-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/base/power/wakeup.c:1219:5: warning: no previous prototype for 'wakeup_sources_stats_open' [-Wmissing-prototypes]
1219 | int wakeup_sources_stats_open(struct inode *inode, struct file *file)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
vim +/wakeup_sources_stats_open +1219 drivers/base/power/wakeup.c
1218
> 1219 int wakeup_sources_stats_open(struct inode *inode, struct file *file)
1220 {
1221 return seq_open_private(file, &wakeup_sources_stats_seq_ops, sizeof(int));
1222 }
1223 EXPORT_SYMBOL_GPL(wakeup_sources_stats_open);
1224
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-24 17:32 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=202610250109.I5tYNwcI-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.