linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Rong Chen <rong.a.chen@intel.com>
Cc: linux-arm-kernel@lists.infradead.org, kbuild-all@lists.01.org,
	kbuild test robot <lkp@intel.com>,
	Sean Christopherson <sean.j.christopherson@intel.com>
Subject: Re: [kbuild-all] Re: [arm-platforms:kvm-arm64/vcpu-xarray 42/49] arch/powerpc/kvm/powerpc.c:792:29: error: 'kvmppc_decrementer_wakeup' defined but not used
Date: Thu, 14 Nov 2019 08:18:53 +0000	[thread overview]
Message-ID: <20191114081853.39e64fc5@why> (raw)
In-Reply-To: <5f2c6f45-1607-c77a-ab08-9723701e9901@intel.com>

On Thu, 14 Nov 2019 08:58:10 +0800
Rong Chen <rong.a.chen@intel.com> wrote:

> On 11/14/19 2:02 AM, Marc Zyngier wrote:
> > On 2019-11-13 17:51, kbuild test robot wrote:  
> >> tree:
> >> https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
> >> kvm-arm64/vcpu-xarray
> >> head:   148748099363327d8cb56aafd386b70ac8c68837
> >> commit: 64e6991c2234c3ba1e36f991302b1bbe1bb791f1 [42/49] KVM: PPC:
> >> Move all vcpu init code into kvm_arch_vcpu_create()
> >> config: powerpc-defconfig (attached as .config)
> >> compiler: powerpc64-linux-gcc (GCC) 7.4.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 64e6991c2234c3ba1e36f991302b1bbe1bb791f1
> >>         # save the attached .config to linux build tree
> >>         GCC_VERSION=7.4.0 make.cross ARCH=powerpc
> >>
> >> If you fix the issue, kindly add following tag
> >> Reported-by: kbuild test robot <lkp@intel.com>  
> >
> > Well, this branch was not supposed to be tested at all...
> > I guess it is too late to take it down :-(
> >
> >         M.  
> 
> Hi Marc,
> 
> Thanks for the explanation, we'll blacklist this branch to avoiding test it again.

Thanks Rong.

For my own education, is there an official way to prevent the kbuild
robot from testing certain branches? Or failing that, a way to tell it
to only send reports to a certain email address instead of spamming
mailing lists for code that is expected to be problematic?

Cheers,

	M.
-- 
Jazz is not dead. It just smells funny...

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-11-14  8:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 17:51 [arm-platforms:kvm-arm64/vcpu-xarray 42/49] arch/powerpc/kvm/powerpc.c:792:29: error: 'kvmppc_decrementer_wakeup' defined but not used kbuild test robot
2019-11-13 18:02 ` Marc Zyngier
2019-11-14  0:58   ` [kbuild-all] " Rong Chen
2019-11-14  8:18     ` Marc Zyngier [this message]
2019-11-14  9:15       ` Rong Chen

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=20191114081853.39e64fc5@why \
    --to=maz@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=rong.a.chen@intel.com \
    --cc=sean.j.christopherson@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).