From: Aaron Lu <aaron.lu@intel.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: "mgorman@suse.de" <mgorman@suse.de>,
"kbuild-all@01.org" <kbuild-all@01.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [aaron:for_lkp_skl_2sp2_test 151/225] drivers/net//ethernet/netronome/nfp/nfp_net_common.c:1188:116: error: '__GFP_COLD' undeclared
Date: Wed, 10 Jan 2018 12:29:23 +0800 [thread overview]
Message-ID: <20180110042923.GA515@intel.com> (raw)
In-Reply-To: <20180110042148.x3nfjnkttdu3irib@wfg-t540p.sh.intel.com>
On Wed, Jan 10, 2018 at 12:21:48PM +0800, Fengguang Wu wrote:
> On Wed, Jan 10, 2018 at 09:34:47AM +0800, Aaron Lu wrote:
> > Please ignore this build report.
> >
> > I thought the robot has done its job but looks like it is still
> > building that branch.
>
> Sorry about that! Although most reports will be caught in the 24 hour,
> the 0-day build bot will nowadays typically continue tests for weeks
> to improve coverage.
Thanks for the explanation.
I have deleted that branch on my tree, I assume that could stop the bot
from building it anymore.
Regards,
Aaron
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-01-10 4:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 22:33 [aaron:for_lkp_skl_2sp2_test 151/225] drivers/net//ethernet/netronome/nfp/nfp_net_common.c:1188:116: error: '__GFP_COLD' undeclared kbuild test robot
2018-01-10 1:34 ` Lu, Aaron
2018-01-10 4:21 ` Fengguang Wu
2018-01-10 4:29 ` Aaron Lu [this message]
2018-01-10 4:36 ` Fengguang Wu
2018-01-10 4:42 ` Fengguang Wu
2018-01-10 4:43 ` Lu, Aaron
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=20180110042923.GA515@intel.com \
--to=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.