linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Santosh Sivaraj <santosh@fossix.org>
Cc: kbuild-all@lists.01.org, kbuild test robot <lkp@intel.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
	Mahesh Salgaonkar <mahesh@linux.ibm.com>,
	Oliver <oohall@gmail.com>, Ganesh Goudar <ganeshgr@linux.ibm.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] papr/scm: Add bad memory ranges to nvdimm bad ranges
Date: Mon, 20 Apr 2020 11:02:36 +0800	[thread overview]
Message-ID: <20200420030236.GG28344@intel.com> (raw)
In-Reply-To: <87a73fiqd5.fsf@santosiv.in.ibm.com>

On Mon, Apr 13, 2020 at 04:50:38PM +0530, Santosh Sivaraj wrote:
> kbuild test robot <lkp@intel.com> writes:
> 
> > Hi Santosh,
> >
> > Thank you for the patch! Yet something to improve:
> >
> > [auto build test ERROR on powerpc/next]
> > [also build test ERROR on v5.7-rc1 next-20200412]
> > [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]
> 
> This patch depends on "powerpc/mce: Add MCE notification chain" [1].
got it, thanks for input, though currently the bot is not able to figure
out this yet for two separated patch sets, here the --base may help.

> 
> [1]: https://lore.kernel.org/linuxppc-dev/20200330071219.12284-1-ganeshgr@linux.ibm.com/
> 
> Thanks,
> Santosh
> 
> >
> > url:    https://github.com/0day-ci/linux/commits/Santosh-Sivaraj/papr-scm-Add-bad-memory-ranges-to-nvdimm-bad-ranges/20200401-171233
> > base:   https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
> > config: powerpc-allyesconfig (attached as .config)
> > compiler: powerpc64-linux-gcc (GCC) 9.3.0
> > reproduce:
> >         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> >         chmod +x ~/bin/make.cross
> >         # save the attached .config to linux build tree
> >         GCC_VERSION=9.3.0 make.cross ARCH=powerpc 
> >
> > 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 >>):
> >
> >    arch/powerpc/platforms/pseries/papr_scm.c: In function 'papr_scm_init':
> >>> arch/powerpc/platforms/pseries/papr_scm.c:584:3: error: implicit declaration of function 'mce_register_notifier'; did you mean 'bus_register_notifier'? [-Werror=implicit-function-declaration]
> >      584 |   mce_register_notifier(&mce_ue_nb);
> >          |   ^~~~~~~~~~~~~~~~~~~~~
> >          |   bus_register_notifier
> >    arch/powerpc/platforms/pseries/papr_scm.c: In function 'papr_scm_exit':
> >>> arch/powerpc/platforms/pseries/papr_scm.c:592:2: error: implicit declaration of function 'mce_unregister_notifier'; did you mean 'bus_unregister_notifier'? [-Werror=implicit-function-declaration]
> >      592 |  mce_unregister_notifier(&mce_ue_nb);
> >          |  ^~~~~~~~~~~~~~~~~~~~~~~
> >          |  bus_unregister_notifier
> >    cc1: some warnings being treated as errors
> >
> > vim +584 arch/powerpc/platforms/pseries/papr_scm.c
> >
> >    577	
> >    578	static int __init papr_scm_init(void)
> >    579	{
> >    580		int ret;
> >    581	
> >    582		ret = platform_driver_register(&papr_scm_driver);
> >    583		if (!ret)
> >  > 584			mce_register_notifier(&mce_ue_nb);
> >    585	
> >    586		return ret;
> >    587	}
> >    588	module_init(papr_scm_init);
> >    589	
> >    590	static void __exit papr_scm_exit(void)
> >    591	{
> >  > 592		mce_unregister_notifier(&mce_ue_nb);
> >    593		platform_driver_unregister(&papr_scm_driver);
> >    594	}
> >    595	module_exit(papr_scm_exit);
> >    596	
> >
> > ---
> > 0-DAY CI Kernel Test Service, Intel Corporation
> > https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
> 

  reply	other threads:[~2020-04-20  3:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01  7:47 [PATCH] papr/scm: Add bad memory ranges to nvdimm bad ranges Santosh Sivaraj
2020-04-09  7:40 ` Santosh Sivaraj
2020-04-13  3:35 ` kbuild test robot
2020-04-13 11:20   ` Santosh Sivaraj
2020-04-20  3:02     ` Philip Li [this message]
2020-04-13 14:24 ` Mahesh J Salgaonkar
2020-04-13 15:37   ` Santosh Sivaraj
2020-04-16  3:41 ` Vaibhav Jain

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=20200420030236.GG28344@intel.com \
    --to=philip.li@intel.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=ganeshgr@linux.ibm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lkp@intel.com \
    --cc=mahesh@linux.ibm.com \
    --cc=oohall@gmail.com \
    --cc=santosh@fossix.org \
    /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).