From: "Li, Philip" <philip.li@intel.com>
To: Dmitry Vyukov <dvyukov@google.com>, lkp <lkp@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"kbuild-all@01.org" <kbuild-all@01.org>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: RE: [kbuild-all] /tmp/ccCNPV4P.s:35: Error: .err encountered
Date: Sun, 13 May 2018 10:45:05 +0000 [thread overview]
Message-ID: <831EE4E5E37DCC428EB295A351E662494CB14775@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CACT4Y+ZZp_QbtFxBfP5dtdx4yfb5FZOWm54fDg=qQQ7u0J=HzQ@mail.gmail.com>
> Subject: Re: [kbuild-all] /tmp/ccCNPV4P.s:35: Error: .err encountered
>
> On Sat, May 12, 2018 at 2:26 PM, kbuild test robot <lkp@intel.com> wrote:
> > bisected to: 05cedaec9b243511f8db62bcd4b1c35c374eba24 arm: port KCOV to
> arm
> > commit date: 12 hours ago
> > config: arm-allmodconfig (attached as .config)
> > compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.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 05cedaec9b243511f8db62bcd4b1c35c374eba24
> > # save the attached .config to linux build tree
> > make.cross ARCH=arm
> >
> > All errors (new ones prefixed by >>):
> >
> > /tmp/ccCNPV4P.s: Assembler messages:
> >>> /tmp/ccCNPV4P.s:35: Error: .err encountered
> > /tmp/ccCNPV4P.s:36: Error: .err encountered
> > /tmp/ccCNPV4P.s:37: Error: .err encountered
>
>
> Hi,
>
> What git tree contains this commit? I fetched all of:
sorry, that we have regression in code which is solved, but it may mess up some data
and leads to missing info like no exact tree mentioned here. We will continue fixing things up.
For the commit itself, the bot caught it from git://git.cmpxchg.org/linux-mmotm.git, which
is one you mentioned below. Is it possible the commit is rebased?
commit 05cedaec9b243511f8db62bcd4b1c35c374eba24
Author: Dmitry Vyukov <dvyukov@google.com>
Date: Sat May 12 00:06:09 2018 +0000
arm: port KCOV to arm
KCOV is code coverage collection facility used, in particular, by
syzkaller system call fuzzer. There is some interest in using syzkaller
on arm devices. So port KCOV to arm.
>
> git://git.cmpxchg.org/linux-mmots.git master
> git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git master
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next-history.git
>
> but I still don't have 05cedaec9b243511f8db62bcd4b1c35c374eba24.
>
> I tried these instructions on the tree which I used to develop the
> patch (on top of git://git.cmpxchg.org/linux-mmots.git), but I got:
>
> make[2]: *** No rule to make target 'drivers/spi/spi-bcm53xx.c',
> needed by 'drivers/spi/spi-bcm53xx.o'. Stop.
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
next prev parent reply other threads:[~2018-05-13 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 12:26 kbuild test robot
2018-05-13 8:52 ` Dmitry Vyukov
2018-05-13 10:45 ` Li, Philip [this message]
2018-05-13 11:59 ` [kbuild-all] " Dmitry Vyukov
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=831EE4E5E37DCC428EB295A351E662494CB14775@shsmsx102.ccr.corp.intel.com \
--to=philip.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@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