From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:mirror-poly-aosp-pixel-malibu-staging 4/4] arch/arm64/kvm/hyp/nvhe/serial.c:42:6: warning: no previous prototype for 'hyp_puts'
Date: Mon, 30 Mar 2026 18:42:21 +0800 [thread overview]
Message-ID: <202603301804.G7ByGunz-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common mirror-poly-aosp-pixel-malibu-staging
head: 5de4567efb4a2a85c5768504b0f45f278e9b13a2
commit: ea53aa5d800829a9adc17df0b6615eb845a9314b [4/4] ANDROID: KVM: arm64: Add serial framework for pKVM
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20260330/202603301804.G7ByGunz-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260330/202603301804.G7ByGunz-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/202603301804.G7ByGunz-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/arm64/kvm/hyp/nvhe/serial.c:42:6: warning: no previous prototype for 'hyp_puts' [-Wmissing-prototypes]
42 | void hyp_puts(const char *s)
| ^~~~~~~~
>> arch/arm64/kvm/hyp/nvhe/serial.c:54:6: warning: no previous prototype for 'hyp_putx64' [-Wmissing-prototypes]
54 | void hyp_putx64(u64 x)
| ^~~~~~~~~~
arch/arm64/kvm/hyp/nvhe/serial.c:60:6: warning: no previous prototype for 'hyp_putc' [-Wmissing-prototypes]
60 | void hyp_putc(char c)
| ^~~~~~~~
>> arch/arm64/kvm/hyp/nvhe/serial.c:66:5: warning: no previous prototype for '__pkvm_register_serial_driver' [-Wmissing-prototypes]
66 | int __pkvm_register_serial_driver(void (*cb)(char))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/hyp_puts +42 arch/arm64/kvm/hyp/nvhe/serial.c
41
> 42 void hyp_puts(const char *s)
43 {
44 if (!hyp_serial_enabled())
45 return;
46
47 while (*s)
48 __hyp_putc(*s++);
49
50 __hyp_putc('\n');
51 __hyp_putc('\r');
52 }
53
> 54 void hyp_putx64(u64 x)
55 {
56 if (hyp_serial_enabled())
57 __hyp_putx4n(x, 64);
58 }
59
60 void hyp_putc(char c)
61 {
62 if (hyp_serial_enabled())
63 __hyp_putc(c);
64 }
65
> 66 int __pkvm_register_serial_driver(void (*cb)(char))
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-30 10:42 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=202603301804.G7ByGunz-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.