linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "kbuild-all@01.org" <kbuild-all@01.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: drivers/gpio/gpiolib.c:3215: undefined reference to `of_get_named_gpiod_flags'
Date: Mon, 12 Sep 2016 21:47:04 +0800	[thread overview]
Message-ID: <20160912134704.f3wjguvzv4c5tekf@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <CACRpkdYzSzmwnYKK5oL-N=L0myjG7PRNY6GVK1NWs04+qRA2aA@mail.gmail.com>

Hi Linus,

On Mon, Sep 12, 2016 at 03:26:22PM +0200, Linus Walleij wrote:
>On Thu, Sep 8, 2016 at 10:07 PM, kbuild test robot
><fengguang.wu@intel.com> wrote:
>
>> reproduce:
>>         git checkout 2527ecc9195e9c66252af24c4689e8a67cd4ccb9
>>         # save the attached .config to linux build tree
>>         make ARCH=um
>
>allyes doesn't work at all for me. No idea how to reproduce this.
>
>I want to fix up the UM build but there are just new bugs popping up
>every time I fix a bug...

How about this option?

        make --keep-going

That's our trick to extend test coverage to as much as possible --
for example, some arch/kconfig combinations actually never succeed.

Thanks,
Fengguang

  reply	other threads:[~2016-09-12 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 20:07 drivers/gpio/gpiolib.c:3215: undefined reference to `of_get_named_gpiod_flags' kbuild test robot
2016-09-12 13:26 ` Linus Walleij
2016-09-12 13:47   ` Fengguang Wu [this message]
2016-09-18  5:22 kbuild test robot
2016-09-23  3:51 kbuild test robot
2016-09-24  2:06 kbuild test robot
2016-10-02  7:03 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=20160912134704.f3wjguvzv4c5tekf@wfg-t540p.sh.intel.com \
    --to=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.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).