All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
	bp@alien8.de, tony.luck@intel.com, aris@redhat.com,
	mchehab@kernel.org, linux-edac@vger.kernel.org
Cc: kbuild-all@lists.01.org, tony.luck@intel.com, aris@redhat.com,
	mchehab@kernel.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH v1 1/1] EDAC, {skx,i10nm}: Use CPU stepping macro to pass configurations
Date: Sun, 10 May 2020 20:29:39 +0800	[thread overview]
Message-ID: <202005102036.mmBM2mW9%lkp@intel.com> (raw)
In-Reply-To: <20200509010822.76331-1-qiuxu.zhuo@intel.com>

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

Hi Qiuxu,

I love your patch! Yet something to improve:

[auto build test ERROR on ras/edac-for-next]
[also build test ERROR on next-20200508]
[cannot apply to v5.7-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Qiuxu-Zhuo/EDAC-skx-i10nm-Use-CPU-stepping-macro-to-pass-configurations/20200509-114154
base:   https://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git edac-for-next
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/edac/i10nm_base.c:138:2: error: implicit declaration of function 'X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS'; did you mean 'X86_MATCH_INTEL_FAM6_MODEL'? [-Werror=implicit-function-declaration]
     X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_TREMONT_D, X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     X86_MATCH_INTEL_FAM6_MODEL
>> drivers/edac/i10nm_base.c:138:39: error: 'ATOM_TREMONT_D' undeclared here (not in a function)
     X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_TREMONT_D, X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
                                          ^~~~~~~~~~~~~~
>> drivers/edac/i10nm_base.c:138:55: error: implicit declaration of function 'X86_STEPPINGS'; did you mean 'CPU_STEPPING_MASK'? [-Werror=implicit-function-declaration]
     X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_TREMONT_D, X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
                                                          ^~~~~~~~~~~~~
                                                          CPU_STEPPING_MASK
>> drivers/edac/i10nm_base.c:140:39: error: 'ICELAKE_X' undeclared here (not in a function)
     X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ICELAKE_X,  X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
                                          ^~~~~~~~~
>> drivers/edac/i10nm_base.c:142:39: error: 'ICELAKE_D' undeclared here (not in a function); did you mean 'ICELAKE_X'?
     X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ICELAKE_D,  X86_STEPPINGS(0x0, 0xf), &i10nm_cfg1),
                                          ^~~~~~~~~
                                          ICELAKE_X
   cc1: some warnings being treated as errors

vim +138 drivers/edac/i10nm_base.c

   136	
   137	static const struct x86_cpu_id i10nm_cpuids[] = {
 > 138		X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_TREMONT_D,	X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
   139		X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_TREMONT_D,	X86_STEPPINGS(0x4, 0xf), &i10nm_cfg1),
 > 140		X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ICELAKE_X,		X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
   141		X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ICELAKE_X,		X86_STEPPINGS(0x4, 0xf), &i10nm_cfg1),
 > 142		X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ICELAKE_D,		X86_STEPPINGS(0x0, 0xf), &i10nm_cfg1),
   143		{}
   144	};
   145	MODULE_DEVICE_TABLE(x86cpu, i10nm_cpuids);
   146	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 73357 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v1 1/1] EDAC, {skx, i10nm}: Use CPU stepping macro to pass configurations
Date: Sun, 10 May 2020 20:29:39 +0800	[thread overview]
Message-ID: <202005102036.mmBM2mW9%lkp@intel.com> (raw)
In-Reply-To: <20200509010822.76331-1-qiuxu.zhuo@intel.com>

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

Hi Qiuxu,

I love your patch! Yet something to improve:

[auto build test ERROR on ras/edac-for-next]
[also build test ERROR on next-20200508]
[cannot apply to v5.7-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Qiuxu-Zhuo/EDAC-skx-i10nm-Use-CPU-stepping-macro-to-pass-configurations/20200509-114154
base:   https://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git edac-for-next
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/edac/i10nm_base.c:138:2: error: implicit declaration of function 'X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS'; did you mean 'X86_MATCH_INTEL_FAM6_MODEL'? [-Werror=implicit-function-declaration]
     X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_TREMONT_D, X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     X86_MATCH_INTEL_FAM6_MODEL
>> drivers/edac/i10nm_base.c:138:39: error: 'ATOM_TREMONT_D' undeclared here (not in a function)
     X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_TREMONT_D, X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
                                          ^~~~~~~~~~~~~~
>> drivers/edac/i10nm_base.c:138:55: error: implicit declaration of function 'X86_STEPPINGS'; did you mean 'CPU_STEPPING_MASK'? [-Werror=implicit-function-declaration]
     X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_TREMONT_D, X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
                                                          ^~~~~~~~~~~~~
                                                          CPU_STEPPING_MASK
>> drivers/edac/i10nm_base.c:140:39: error: 'ICELAKE_X' undeclared here (not in a function)
     X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ICELAKE_X,  X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
                                          ^~~~~~~~~
>> drivers/edac/i10nm_base.c:142:39: error: 'ICELAKE_D' undeclared here (not in a function); did you mean 'ICELAKE_X'?
     X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ICELAKE_D,  X86_STEPPINGS(0x0, 0xf), &i10nm_cfg1),
                                          ^~~~~~~~~
                                          ICELAKE_X
   cc1: some warnings being treated as errors

vim +138 drivers/edac/i10nm_base.c

   136	
   137	static const struct x86_cpu_id i10nm_cpuids[] = {
 > 138		X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_TREMONT_D,	X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
   139		X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_TREMONT_D,	X86_STEPPINGS(0x4, 0xf), &i10nm_cfg1),
 > 140		X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ICELAKE_X,		X86_STEPPINGS(0x0, 0x3), &i10nm_cfg0),
   141		X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ICELAKE_X,		X86_STEPPINGS(0x4, 0xf), &i10nm_cfg1),
 > 142		X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ICELAKE_D,		X86_STEPPINGS(0x0, 0xf), &i10nm_cfg1),
   143		{}
   144	};
   145	MODULE_DEVICE_TABLE(x86cpu, i10nm_cpuids);
   146	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 73357 bytes --]

  reply	other threads:[~2020-05-10 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09  1:08 [PATCH v1 1/1] EDAC, {skx,i10nm}: Use CPU stepping macro to pass configurations Qiuxu Zhuo
2020-05-10 12:29 ` kbuild test robot [this message]
2020-05-10 12:29   ` [PATCH v1 1/1] EDAC, {skx, i10nm}: " kbuild test robot
2020-05-10 19:37 ` [PATCH v1 1/1] EDAC, {skx,i10nm}: " kbuild test robot
2020-05-10 19:37   ` [PATCH v1 1/1] EDAC, {skx, i10nm}: " kbuild test robot

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=202005102036.mmBM2mW9%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aris@redhat.com \
    --cc=bp@alien8.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=qiuxu.zhuo@intel.com \
    --cc=tony.luck@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 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.