From: christophe leroy <christophe.leroy@c-s.fr>
To: Scott Wood <oss@buserror.net>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v7] powerpc32: provide VIRT_CPU_ACCOUNTING
Date: Tue, 23 Feb 2016 20:32:26 +0100 [thread overview]
Message-ID: <56CCB3CA.6020908@c-s.fr> (raw)
In-Reply-To: <1456255707.5360.17.camel@buserror.net>
Le 23/02/2016 20:28, Scott Wood a écrit :
> On Wed, 2016-02-24 at 02:38 +0800, kbuild test robot wrote:
>> Hi Christophe,
>>
>> [auto build test ERROR on powerpc/next]
>> [also build test ERROR on v4.5-rc5 next-20160223]
>> [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/Christophe-Leroy/powerpc32-
>> provide-VIRT_CPU_ACCOUNTING/20160224-010322
>> base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git ne
>> xt
>> config: powerpc-defconfig (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=powerpc
> I've been seeing a lot of these build failure reports from your patches -- can
> you please test build on an appropriate variety of configs before submitting?
>
>
I usually test several PPC32 configs, but I only have a PPC32 compiler,
therefore I'm not able to test PPC64 configs.
I'll see what I can do.
Christophe
---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2016-02-23 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 16:59 [PATCH v7] powerpc32: provide VIRT_CPU_ACCOUNTING Christophe Leroy
2016-02-23 18:38 ` kbuild test robot
2016-02-23 19:28 ` Scott Wood
2016-02-23 19:32 ` christophe leroy [this message]
2016-02-23 19:33 ` Scott Wood
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=56CCB3CA.6020908@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
/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.