From: "Li, Philip" <philip.li@intel.com>
To: Michal Hocko <mhocko@suse.com>, lkp <lkp@intel.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
"kbuild-all@01.org" <kbuild-all@01.org>
Subject: RE: [kbuild-all] [memcg:since-4.16 207/224] arch/tile/mm/mmap.c:53:6: error: conflicting types for 'arch_pick_mmap_layout'
Date: Wed, 11 Apr 2018 12:25:03 +0000 [thread overview]
Message-ID: <831EE4E5E37DCC428EB295A351E662494CAA60E6@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20180411113349.GI23400@dhcp22.suse.cz>
> On Wed 11-04-18 19:16:50, kbuild test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git since-4.16
> > head: e5edc6faef45baae632fc4c76096a2ab69145c11
> > commit: a18ed29e39bde6c1aaf0fb449732ba8423bc5964 [207/224] exec: pass
> stack rlimit into mm layout functions
> > config: tile-tilegx_defconfig (attached as .config)
> > compiler: tilegx-linux-gcc (GCC) 7.2.0
> > reproduce:
> > wget https://raw.githubusercontent.com/intel/lkp-
> tests/master/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > git checkout a18ed29e39bde6c1aaf0fb449732ba8423bc5964
> > # save the attached .config to linux build tree
> > make.cross ARCH=tile
> >
> > All errors (new ones prefixed by >>):
> >
> > >> arch/tile/mm/mmap.c:53:6: error: conflicting types for
> 'arch_pick_mmap_layout'
> > void arch_pick_mmap_layout(struct mm_struct *mm)
>
> Isn't tile dead? Does it make any sense to compile test it?
thanks for feedback, we will look into this and remove the non-supported archs.
> --
> Michal Hocko
> SUSE Labs
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
prev parent reply other threads:[~2018-04-11 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 11:16 kbuild test robot
2018-04-11 11:33 ` Michal Hocko
2018-04-11 12:25 ` Li, Philip [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=831EE4E5E37DCC428EB295A351E662494CAA60E6@shsmsx102.ccr.corp.intel.com \
--to=philip.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mhocko@suse.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