linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Piotr Henryk Dabrowski <ultr@ultr.pl>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Piotr Henryk Dabrowski <ultr@ultr.pl>
Subject: Re: [PATCH] cpu-= command line parmeter, SYS_cpuid sys call, kernel-adjusted CPUID
Date: Fri, 11 Mar 2016 05:08:09 +0800	[thread overview]
Message-ID: <201603110554.5tsT4ZwQ%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160310212716.3711abfc@ultra.tux-net>

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

Hi Piotr,

[auto build test WARNING on next-20160310]
[cannot apply to tip/x86/core v4.5-rc7 v4.5-rc6 v4.5-rc5 v4.5-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Piotr-Henryk-Dabrowski/cpu-command-line-parmeter-SYS_cpuid-sys-call-kernel-adjusted-CPUID/20160311-043022
config: xtensa-allyesconfig (attached as .config)
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=xtensa 

All warnings (new ones prefixed by >>):

   <stdin>:1298:2: warning: #warning syscall userfaultfd not implemented [-Wcpp]
   <stdin>:1301:2: warning: #warning syscall membarrier not implemented [-Wcpp]
   <stdin>:1304:2: warning: #warning syscall mlock2 not implemented [-Wcpp]
   <stdin>:1307:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]
   <stdin>:1310:2: warning: #warning syscall madvisev not implemented [-Wcpp]
>> <stdin>:1313:2: warning: #warning syscall cpuid not implemented [-Wcpp]

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 44760 bytes --]

  parent reply	other threads:[~2016-03-10 21:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 20:27 [PATCH] cpu-= command line parmeter, SYS_cpuid sys call, kernel-adjusted CPUID Piotr Henryk Dabrowski
2016-03-10 20:38 ` kbuild test robot
2016-03-10 21:08 ` kbuild test robot [this message]
2016-03-10 22:27 ` kbuild test robot
2016-03-11  0:13 ` [PATCH v2] " Piotr Henryk Dabrowski
2016-03-11  0:25   ` kbuild test robot
2016-03-11  0:52   ` kbuild test robot
2016-03-12  1:12 ` [PATCH v3] " Piotr Henryk Dabrowski
2016-03-12 19:31   ` Henrique de Moraes Holschuh
2016-03-14 16:06     ` Piotr Henryk Dabrowski

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=201603110554.5tsT4ZwQ%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ultr@ultr.pl \
    /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).