From: Arnd Bergmann <arnd@arndb.de>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, huangdaode <huangdaode@hisilicon.com>,
davem@davemloft.net, joe@perches.com, liguozhu@hisilicon.com,
Yisen.Zhuang@huawei.com, netdev@vger.kernel.org,
linuxarm@huawei.com, salil.mehta@huawei.com,
kenneth-lee-2012@foxmail.com, xuwei5@hisilicon.com,
lisheng011@huawei.com, linux-kernel@vger.kernel.org,
lipeng321@huawei.com
Subject: Re: [PATCH] net: hisilicon: add OF dependency
Date: Fri, 16 Oct 2015 21:10:54 +0200 [thread overview]
Message-ID: <3752954.ncYqAxKXIS@wuerfel> (raw)
In-Reply-To: <201510170250.9XPqjohi%fengguang.wu@intel.com>
On Saturday 17 October 2015 02:39:51 kbuild test robot wrote:
>
> [auto build test WARNING on net-next/master -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
>
> url: https://github.com/0day-ci/linux/commits/Arnd-Bergmann/net-hisilicon-add-OF-dependency/20151016-173818
> config: ia64-allmodconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=ia64
>
I guess I should have sent my three patches as a series. The build bot
found the same two bugs I had found myself and sent fixes for, but
applying the 'add OF dependency' without the other two makes them appear
in more configurations.
For all I can see, the two reports here are fixed if all three of my
patches are applied.
Arnd
next prev parent reply other threads:[~2015-10-16 19:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 3:54 [PATCH net-next v3 0/2] net: hisilicon fix some bugs in HNS drivers huangdaode
2015-10-16 3:54 ` [PATCH net-next v3 1/2] net: hisilicon rm hnae sysfs interface huangdaode
2015-10-16 9:19 ` Arnd Bergmann
2015-10-16 3:54 ` [PATCH net-next v3 2/2] net: hisilicon fix a bug on Hisilicon Network Subsystem huangdaode
2015-10-16 9:30 ` [PATCH net-next v3 0/2] net: hisilicon fix some bugs in HNS drivers Arnd Bergmann
2015-10-19 2:23 ` huangdaode
2015-10-16 9:30 ` [PATCH] net: hisilicon: include linux/vmalloc.h in dsaf Arnd Bergmann
2015-10-19 2:59 ` David Miller
2015-10-16 9:33 ` [PATCH] net: hisilicon: add OF dependency Arnd Bergmann
2015-10-16 17:03 ` kbuild test robot
2015-10-16 18:16 ` kbuild test robot
2015-10-16 18:22 ` Joe Perches
2015-10-16 18:39 ` kbuild test robot
2015-10-16 19:10 ` Arnd Bergmann [this message]
2015-10-19 3:01 ` David Miller
2015-10-16 10:00 ` [PATCH] net: hix5hd2_gmac: avoid integer overload warning Arnd Bergmann
2015-10-16 11:14 ` David Laight
2015-10-16 11:28 ` Arnd Bergmann
2015-10-16 18:04 ` Joe Perches
2015-10-16 18:50 ` Sergei Shtylyov
2015-10-16 21:22 ` Joe Perches
2015-10-16 21:42 ` Arnd Bergmann
2015-10-19 3:01 ` David Miller
2015-10-19 2:55 ` [PATCH net-next v3 0/2] net: hisilicon fix some bugs in HNS drivers David Miller
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=3752954.ncYqAxKXIS@wuerfel \
--to=arnd@arndb.de \
--cc=Yisen.Zhuang@huawei.com \
--cc=davem@davemloft.net \
--cc=huangdaode@hisilicon.com \
--cc=joe@perches.com \
--cc=kbuild-all@01.org \
--cc=kenneth-lee-2012@foxmail.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=lisheng011@huawei.com \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=xuwei5@hisilicon.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;
as well as URLs for NNTP newsgroup(s).