From: kbuild test robot <lkp@intel.com>
To: Niranjan Dighe <niranjan.dighe@gmail.com>
Cc: kbuild-all@01.org, Peter.Chen@freescale.com,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] chipidea: Fix issue in reconnecing gadget without insmod/rmmod
Date: Wed, 12 Apr 2017 01:17:39 +0800 [thread overview]
Message-ID: <201704120101.Ek6xhBc5%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170411151624.GA4703@scoobydoo>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
Hi Niranjan,
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.11-rc6]
[cannot apply to next-20170411]
[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/Niranjan-Dighe/chipidea-Fix-issue-in-reconnecing-gadget-without-insmod-rmmod/20170411-235845
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
config: x86_64-acpi-redef (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=x86_64
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `ci_role_write':
>> debug.c:(.text+0x56ca41): undefined reference to `ci_hdrc_otg_fsm_restart'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29540 bytes --]
next prev parent reply other threads:[~2017-04-11 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 15:16 Niranjan Dighe
2017-04-11 17:17 ` kbuild test robot [this message]
2017-04-11 18:22 ` kbuild test robot
2017-04-12 11:51 ` Peter Chen
2017-04-12 12:48 ` Niranjan Dighe
2017-04-14 9:38 ` Peter Chen
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=201704120101.Ek6xhBc5%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Peter.Chen@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=niranjan.dighe@gmail.com \
/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
all inboxes | Powered by JetHome®