From: "Lu, Aaron" <aaron.lu@intel.com>
To: "Wu, Fengguang" <fengguang.wu@intel.com>
Cc: "kbuild-all@01.org" <kbuild-all@01.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"mgorman@suse.de" <mgorman@suse.de>,
"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 04:43:18 +0000 [thread overview]
Message-ID: <1515559436.32635.0.camel@intel.com> (raw)
In-Reply-To: <20180110044218.gq5nxa4cuvqpamlg@wfg-t540p.sh.intel.com>
On Wed, 2018-01-10 at 12:42 +0800, Fengguang Wu wrote:
> > I just removed the branch, there should be no more such reports.
>
> The other option is to add "rfc" or "RFC" somewhere in the branch
> name. I'll mark such branches as private reporting ones.
Well that's cool, thanks a lot!
prev parent reply other threads:[~2018-01-10 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 22:33 kbuild test robot
2018-01-10 1:34 ` Lu, Aaron
2018-01-10 4:21 ` Fengguang Wu
2018-01-10 4:29 ` Aaron Lu
2018-01-10 4:36 ` Fengguang Wu
2018-01-10 4:42 ` Fengguang Wu
2018-01-10 4:43 ` Lu, Aaron [this message]
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=1515559436.32635.0.camel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox