From: 김준수 <iamjoonsoo.kim@lge.com>
To: 'kbuild test robot' <fengguang.wu@intel.com>
Cc: 'Linux Memory Management List' <linux-mm@kvack.org>,
'Andrew Morton' <akpm@linux-foundation.org>,
kbuild-all@01.org
Subject: RE: [next:master 103/212] make[2]: *** No rule to make target `arch/powerpc/kvm/book3s_hv_cma.o', needed by `arch/powerpc/kvm/built-in.o'.
Date: Tue, 24 Jun 2014 15:23:45 +0900 [thread overview]
Message-ID: <005c01cf8f74$da4866b0$8ed93410$@lge.com> (raw)
In-Reply-To: <53a8fd43.3YaWacNnJ4rMjQ6L%fengguang.wu@intel.com>
> -----Original Message-----
> From: kbuild test robot [mailto:fengguang.wu@intel.com]
> Sent: Tuesday, June 24, 2014 1:24 PM
> To: Joonsoo Kim
> Cc: Linux Memory Management List; Andrew Morton; kbuild-all@01.org
> Subject: [next:master 103/212] make[2]: *** No rule to make target
> `arch/powerpc/kvm/book3s_hv_cma.o', needed by `arch/powerpc/kvm/built-
> in.o'.
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> master
> head: 58ae500a03a6bf68eee323c342431bfdd3f460b6
> commit: e58e263e5254df63f3997192322220748e4f6223 [103/212] PPC, KVM, CMA:
> use general CMA reserved area management framework
> config: make ARCH=powerpc ppc64_defconfig
>
> All error/warnings:
>
> >> make[2]: *** No rule to make target `arch/powerpc/kvm/book3s_hv_cma.o',
> needed by `arch/powerpc/kvm/built-in.o'.
> make[2]: Target `__build' not remade because of errors.
Thanks for reporting.
Here goes trivial fix!
-------------->8----------------------
prev parent reply other threads:[~2014-06-24 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 4:23 [next:master 103/212] make[2]: *** No rule to make target `arch/powerpc/kvm/book3s_hv_cma.o', needed by `arch/powerpc/kvm/built-in.o' kbuild test robot
2014-06-24 6:23 ` 김준수 [this message]
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='005c01cf8f74$da4866b0$8ed93410$@lge.com' \
--to=iamjoonsoo.kim@lge.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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 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.