From: kernel test robot <lkp@intel.com>
To: Dan Raymond <draymond@foxvalley.net>,
linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v1] arch/x86: port I/O tracing on x86
Date: Wed, 20 Sep 2023 01:26:27 +0800 [thread overview]
Message-ID: <202309200143.Me2RTikv-lkp@intel.com> (raw)
In-Reply-To: <14c27df7-12a3-e432-a741-17672185c092@foxvalley.net>
Hi Dan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on be8b93b5cc7d533eb8c9b0590cdac055ecafe13a]
url: https://github.com/intel-lab-lkp/linux/commits/Dan-Raymond/arch-x86-port-I-O-tracing-on-x86/20230919-015640
base: be8b93b5cc7d533eb8c9b0590cdac055ecafe13a
patch link: https://lore.kernel.org/r/14c27df7-12a3-e432-a741-17672185c092%40foxvalley.net
patch subject: [PATCH v1] arch/x86: port I/O tracing on x86
config: x86_64-buildonly-randconfig-001-20230919 (https://download.01.org/0day-ci/archive/20230920/202309200143.Me2RTikv-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230920/202309200143.Me2RTikv-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/202309200143.Me2RTikv-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/lib/trace_portio.c:6:6: warning: no previous prototype for 'do_trace_portio_read' [-Wmissing-prototypes]
6 | void do_trace_portio_read(u32 value, u16 port, char width, long ip_addr)
| ^~~~~~~~~~~~~~~~~~~~
>> arch/x86/lib/trace_portio.c:13:6: warning: no previous prototype for 'do_trace_portio_write' [-Wmissing-prototypes]
13 | void do_trace_portio_write(u32 value, u16 port, char width, long ip_addr)
| ^~~~~~~~~~~~~~~~~~~~~
vim +/do_trace_portio_read +6 arch/x86/lib/trace_portio.c
5
> 6 void do_trace_portio_read(u32 value, u16 port, char width, long ip_addr)
7 {
8 trace_portio_read(value, port, width, ip_addr);
9 }
10 EXPORT_SYMBOL_GPL(do_trace_portio_read);
11 EXPORT_TRACEPOINT_SYMBOL_GPL(portio_read);
12
> 13 void do_trace_portio_write(u32 value, u16 port, char width, long ip_addr)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-19 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 17:55 [PATCH v1] arch/x86: port I/O tracing on x86 Dan Raymond
2023-09-19 17:26 ` kernel test robot
2023-09-19 19:30 ` Dan Raymond
2023-09-20 0:31 ` Dan Raymond
2023-09-19 17:26 ` kernel test robot [this message]
2023-09-19 19:43 ` Peter Zijlstra
2023-09-19 19:56 ` Dan Raymond
2023-09-19 21:12 ` Peter Zijlstra
2023-09-19 21:31 ` Dan Raymond
2023-09-19 22:43 ` Dan Raymond
2023-09-21 17:07 ` Dan Raymond
2023-09-25 21:10 ` Dan Raymond
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=202309200143.Me2RTikv-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=draymond@foxvalley.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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