From: Michal Hocko <mhocko@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Eric Dumazet <edumazet@google.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: use kvmalloc rather than open coded variant
Date: Sat, 7 Jan 2017 10:19:50 +0100 [thread overview]
Message-ID: <20170107091949.GA5047@dhcp22.suse.cz> (raw)
In-Reply-To: <201701071152.Do5cZJAt%fengguang.wu@intel.com>
On Sat 07-01-17 11:33:15, kbuild test robot wrote:
> Hi Michal,
>
> [auto build test ERROR on net-next/master]
> [also build test ERROR on v4.10-rc2 next-20170106]
> [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/Michal-Hocko/net-use-kvmalloc-rather-than-open-coded-variant/20170107-104105
> config: x86_64-randconfig-i0-201701 (attached as .config)
> compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> Note: the linux-review/Michal-Hocko/net-use-kvmalloc-rather-than-open-coded-variant/20170107-104105 HEAD 29df6a817f53555953b47c6f8d09397f9f7b598c builds fine.
> It only hurts bisectibility.
This patch depends on
http://lkml.kernel.org/r/20170102133700.1734-1-mhocko@kernel.org
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-01-07 9:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 15:20 __GFP_REPEAT usage in fq_alloc_node Michal Hocko
2017-01-06 15:39 ` Eric Dumazet
2017-01-06 16:07 ` Michal Hocko
2017-01-06 16:19 ` Michal Hocko
2017-01-07 3:33 ` [PATCH] net: use kvmalloc rather than open coded variant kbuild test robot
2017-01-07 9:19 ` Michal Hocko [this message]
2017-01-07 3:35 ` kbuild test robot
2017-01-09 10:22 ` __GFP_REPEAT usage in fq_alloc_node Michal Hocko
2017-01-09 16:00 ` Eric Dumazet
2017-01-09 17:45 ` Michal Hocko
2017-01-09 17:53 ` Eric Dumazet
2017-01-14 23:43 ` [PATCH] net_sched: use kvmalloc rather than opencoded variant kbuild test robot
2017-01-16 8:54 ` Michal Hocko
2017-01-06 16:31 ` __GFP_REPEAT usage in fq_alloc_node Vlastimil Babka
2017-01-06 16:48 ` Eric Dumazet
2017-01-06 16:50 ` Eric Dumazet
2017-01-06 16:55 ` Vlastimil Babka
2017-01-06 17:08 ` Eric Dumazet
2017-01-06 17:18 ` Vlastimil Babka
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=20170107091949.GA5047@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=edumazet@google.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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).