From: Davidlohr Bueso <dave@stgolabs.net>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [next:master 10274/10671] /kbuild/src/slow3/arch/arm/mach-tegra/cpuidle-tegra114.c:88: undefined reference to `psci_smp_available'
Date: Thu, 11 Jun 2015 15:12:37 -0700 [thread overview]
Message-ID: <1434060757.3165.96.camel@stgolabs.net> (raw)
In-Reply-To: <201506120455.HwpOSg84%fengguang.wu@intel.com>
On Fri, 2015-06-12 at 04:45 +0800, kbuild test robot wrote:
> Hi Davidlohr,
>
> First bad commit (maybe != root cause):
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: f0939c364ffe7dc377c4d7946360f99cb7fc867b
> commit: 48803a970534ad0411991de1d293996db8ea9aa0 [10274/10671] ipc,sysv: return -EINVAL upon incorrect id/seqnum
The below makes no sense with this commit. `psci_smp_available' has 0 to
do with ipc.
>
> All error/warnings (new ones prefixed by >>):
>
> arch/arm/mach-tegra/built-in.o: In function `tegra114_cpuidle_init':
> >> /kbuild/src/slow3/arch/arm/mach-tegra/cpuidle-tegra114.c:88: undefined reference to `psci_smp_available'
Thanks,
Davidlohr
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-06-11 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 20:45 kbuild test robot
2015-06-11 22:12 ` Davidlohr Bueso [this message]
2015-06-12 0:52 ` Fengguang Wu
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=1434060757.3165.96.camel@stgolabs.net \
--to=dave@stgolabs.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox