From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Chunyan Zhang <zhang.chunyan@linaro.org>
Subject: Re: [PATCH] kernel: trace: pass export pointer as argument to ->write()
Date: Fri, 02 Jun 2017 13:14:27 +0300 [thread overview]
Message-ID: <877f0uvgqk.fsf@linux.intel.com> (raw)
In-Reply-To: <201705181922.glbnZKEM%fengguang.wu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
Hi,
kbuild test robot <lkp@intel.com> writes:
> Hi Felipe,
>
> [auto build test ERROR on tip/perf/core]
> [also build test ERROR on v4.12-rc1 next-20170518]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Felipe-Balbi/kernel-trace-pass-export-pointer-as-argument-to-write/20170518-135452
> config: i386-allmodconfig (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
> drivers/hwtracing/stm/ftrace.c: In function 'stm_ftrace_write':
>>> drivers/hwtracing/stm/ftrace.c:49:19: error: incompatible type for argument 1 of 'stm_source_write'
> stm_source_write(stm->data, STM_FTRACE_CHAN, buf, len);
> ^~~
> In file included from drivers/hwtracing/stm/ftrace.c:18:0:
> include/linux/stm.h:136:13: note: expected 'struct stm_source_data *' but argument is of type 'struct stm_source_data'
> int notrace stm_source_write(struct stm_source_data *data, unsigned int chan,
> ^~~~~~~~~~~~~~~~
>
> vim +/stm_source_write +49 drivers/hwtracing/stm/ftrace.c
>
> 43 */
> 44 static void notrace
> 45 stm_ftrace_write(struct trace_export *export, const void *buf, unsigned int len)
> 46 {
> 47 struct stm_ftrace *stm = container_of(export, struct stm_ftrace, ftrace);
> 48
> > 49 stm_source_write(stm->data, STM_FTRACE_CHAN, buf, len);
sorry, just came back from vacations and noticed this. I'll send a v2 shortly.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-06-02 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 8:05 [PATCH] kernel: trace: pass export pointer as argument to ->write() Felipe Balbi
2017-05-17 13:43 ` Steven Rostedt
2017-05-18 2:26 ` Chunyan Zhang
2017-05-18 2:52 ` Steven Rostedt
2017-12-04 12:09 ` Steven Rostedt
[not found] ` <20171204122312.tyxq54jmy7vijlmo@ukko.fi.intel.com>
2017-12-08 10:46 ` Felipe Balbi
2017-05-18 11:10 ` kbuild test robot
2017-06-02 10:14 ` Felipe Balbi [this message]
2017-06-02 10:20 ` [PATCH v2] " Felipe Balbi
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=877f0uvgqk.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=zhang.chunyan@linaro.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.