From: Rong Chen <rong.a.chen@intel.com>
To: Roman Gushchin <guro@fb.com>, Qian Cai <cai@lca.pw>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild test robot <lkp@intel.com>,
"kbuild-all@01.org" <kbuild-all@01.org>
Subject: Re: [kbuild-all] [rgushchin:fix_vmstats 21/221] include/asm-generic/5level-fixup.h:14:18: error: unknown type name 'pgd_t'; did you mean 'pid_t'?
Date: Tue, 20 Aug 2019 15:08:43 +0800 [thread overview]
Message-ID: <3edbc032-4cc3-a87c-03c9-2b2fcaec32e8@intel.com> (raw)
In-Reply-To: <20190814004548.GA18813@tower.DHCP.thefacebook.com>
On 8/14/19 8:45 AM, Roman Gushchin wrote:
> On Tue, Aug 13, 2019 at 10:52:25AM -0400, Qian Cai wrote:
>> On Tue, 2019-08-13 at 11:33 +0800, kbuild test robot wrote:
>>> tree: https://github.com/rgushchin/linux.git fix_vmstats
>>> head: 4ec858b5201ae067607e82706b36588631c1b990
>>> commit: 938dda772d9d05074bfe1baa0dc18873fbf4fedb [21/221] include/asm-
>>> generic/5level-fixup.h: fix variable 'p4d' set but not used
>>> config: parisc-c3000_defconfig (attached as .config)
>>> compiler: hppa-linux-gcc (GCC) 7.4.0
>>> reproduce:
>>> wget https://urldefense.proofpoint.com/v2/url?u=https-3A__raw.githubusercontent.com_intel_lkp-2Dtests_master_sbin_mak&d=DwIFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=jJYgtDM7QT-W-Fz_d29HYQ&m=TOir6b4wrmTSQpeaAQcpcHZUk9uWkTRUOJaNgbh4m-o&s=0IeTTEfMlxl9cDI9YAz2Zji8QaiE8B29qreDUnvID5E&e=
>>> e.cross -O ~/bin/make.cross
>>> chmod +x ~/bin/make.cross
>>> git checkout 938dda772d9d05074bfe1baa0dc18873fbf4fedb
>>> # save the attached .config to linux build tree
>>> GCC_VERSION=7.4.0 make.cross ARCH=parisc
>> I am unable to reproduce this on today's linux-next tree. What's point of
>> testing this particular personal git tree/branch?
> I'm using it to test my patches before sending them to public mailing lists.
> It really helps with reducing the number of trivial issues and upstream
> iterations as a consequence. And not only trivial...
>
> If there is a way to prevent notifying anyone but me, please, let me know,
> I'm happy to do it.
>
Hi Roman,
The reports should only be sent to you now. please see
https://github.com/intel/lkp-tests/blob/master/repo/linux/rgushchin
Best Regards,
Rong Chen
next prev parent reply other threads:[~2019-08-20 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 3:33 [rgushchin:fix_vmstats 21/221] include/asm-generic/5level-fixup.h:14:18: error: unknown type name 'pgd_t'; did you mean 'pid_t'? kbuild test robot
2019-08-13 14:52 ` Qian Cai
2019-08-14 0:45 ` Roman Gushchin
2019-08-14 14:38 ` Qian Cai
2019-08-20 7:08 ` Rong Chen [this message]
2019-08-22 0:32 ` [kbuild-all] " Roman Gushchin
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=3edbc032-4cc3-a87c-03c9-2b2fcaec32e8@intel.com \
--to=rong.a.chen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.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).