From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-serial@vger.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
gnomes@lxorguk.ukuu.org.uk, andy.shevchenko@gmail.com,
Rob Groner <rgroner@rtd.com>
Subject: Re: [PATCH v4] serial: 8250: add gpio support to exar
Date: Mon, 18 Jan 2016 23:05:12 +0800 [thread overview]
Message-ID: <201601182326.iqgh1O26%fengguang.wu@intel.com> (raw)
In-Reply-To: <1453119038-11741-1-git-send-email-sudipm.mukherjee@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Hi Sudip,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.4 next-20160118]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Sudip-Mukherjee/serial-8250-add-gpio-support-to-exar/20160118-201411
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-next
config: i386-allyesconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> make[3]: *** No rule to make target 'drivers/gpio/gpio-exar.o', needed by 'drivers/gpio/built-in.o'.
make[3]: Target '__build' not remade because of errors.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 51979 bytes --]
next prev parent reply other threads:[~2016-01-18 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 12:10 [PATCH v4] serial: 8250: add gpio support to exar Sudip Mukherjee
2016-01-18 13:39 ` Andy Shevchenko
2016-01-18 14:06 ` Sudip Mukherjee
2016-01-18 15:05 ` kbuild test robot [this message]
2016-01-18 17:24 ` kbuild test robot
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=201601182326.iqgh1O26%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rgroner@rtd.com \
--cc=sudipm.mukherjee@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