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 USB <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Chunyan Zhang <zhang.chunyan@linaro.org>
Subject: Re: [PATCH] usb: gadget: functions: add ftrace export over USB
Date: Mon, 12 Jun 2017 13:39:09 +0300 [thread overview]
Message-ID: <87vao1pk1e.fsf@linux.intel.com> (raw)
In-Reply-To: <201706101133.p5zuarNi%fengguang.wu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
Hi,
kbuild test robot <lkp@intel.com> writes:
> Hi Felipe,
>
> [auto build test ERROR on balbi-usb/next]
> [also build test ERROR on v4.12-rc4 next-20170609]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
this patch depends on another patch [1] in order to compile properly :-)
[1] https://marc.info/?i=20170602102025.5140-1-felipe.balbi@linux.intel.com
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-06-12 10:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 6:13 [PATCH] usb: gadget: functions: add ftrace export over USB Felipe Balbi
2017-06-09 10:28 ` Felipe Balbi
2017-06-09 11:15 ` Felipe Balbi
2017-07-14 5:52 ` Pratyush Anand
2017-07-14 6:53 ` Felipe Balbi
2017-07-14 21:44 ` Steven Rostedt
2017-06-09 14:02 ` Steven Rostedt
2017-06-09 14:05 ` Felipe Balbi
2017-06-09 15:07 ` Steven Rostedt
2017-06-10 3:38 ` kbuild test robot
2017-06-12 10:39 ` Felipe Balbi [this message]
2017-06-10 4:02 ` kbuild test robot
2017-07-13 11:40 ` Felipe Balbi
2017-07-14 5:31 ` Pratyush Anand
2017-07-14 6:56 ` Felipe Balbi
2019-03-21 9:38 ` Felipe Balbi
2019-03-21 16:37 ` Steven Rostedt
2019-03-22 11:49 ` Felipe Balbi
2019-03-22 12:22 ` Steven Rostedt
2019-03-22 12:27 ` 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=87vao1pk1e.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=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).