From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [sashal-linux-stable:queue-4.9 47/79] drivers//hwtracing/coresight/coresight-tmc-etf.c:295:10: error: 'event' undeclared; did you mean 'io_event'?
Date: Sat, 11 Jan 2020 00:04:36 +0800 [thread overview]
Message-ID: <202001110014.ADksX9dK%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2203 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git queue-4.9
head: 4148278970e6bb725edb3fd5cc91c3d83cc16a97
commit: 6e0398880e744cdd7e8ea21c830d010dd62e8582 [47/79] coresight: tmc-etf: Do not call smp_processor_id from preemptible
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 6e0398880e744cdd7e8ea21c830d010dd62e8582
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers//hwtracing/coresight/coresight-tmc-etf.c: In function 'tmc_alloc_etf_buffer':
>> drivers//hwtracing/coresight/coresight-tmc-etf.c:295:10: error: 'event' undeclared (first use in this function); did you mean 'io_event'?
node = (event->cpu == -1) ? NUMA_NO_NODE : cpu_to_node(event->cpu);
^~~~~
io_event
drivers//hwtracing/coresight/coresight-tmc-etf.c:295:10: note: each undeclared identifier is reported only once for each function it appears in
vim +295 drivers//hwtracing/coresight/coresight-tmc-etf.c
288
289 static void *tmc_alloc_etf_buffer(struct coresight_device *csdev, int cpu,
290 void **pages, int nr_pages, bool overwrite)
291 {
292 int node;
293 struct cs_buffers *buf;
294
> 295 node = (event->cpu == -1) ? NUMA_NO_NODE : cpu_to_node(event->cpu);
296
297 /* Allocate memory structure for interaction with Perf */
298 buf = kzalloc_node(sizeof(struct cs_buffers), GFP_KERNEL, node);
299 if (!buf)
300 return NULL;
301
302 buf->snapshot = overwrite;
303 buf->nr_pages = nr_pages;
304 buf->data_pages = pages;
305
306 return buf;
307 }
308
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 52091 bytes --]
reply other threads:[~2020-01-10 16:04 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=202001110014.ADksX9dK%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.