linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: build failure: linux-next: ARM/SH-mobile defconfigs: kota2, marzen
Date: Wed, 29 May 2013 07:30:14 -0700	[thread overview]
Message-ID: <877gihamfd.fsf@linaro.org> (raw)
In-Reply-To: <20130529020550.GC16836@verge.net.au> (Simon Horman's message of "Wed, 29 May 2013 11:05:51 +0900")

Simon Horman <horms@verge.net.au> writes:

> On Tue, May 28, 2013 at 03:57:01PM -0700, Kevin Hilman wrote:
>> Hello,
>> 
>> Both kota2_defconfig and marzen_defconfig started failing in the most
>> recnet linux-next (next-20130527) but were successful in the previous
>> build (next-20130523).
>> 
>> Both fail wit this error:
>> 
>> drivers/built-in.o: In function `sh_mobile_sdhi_probe':
>> /work/kernel/next/drivers/mmc/host/sh_mobile_sdhi.c:170: undefined reference to `shdma_chan_filter'
>> make[1]: *** [vmlinux] Error 1
>> make[1]: Target `_all' not remade because of errors.
>> 
>> Full build logs are available here:
>> 
>>   https://ci.linaro.org/jenkins/job/khilman-kernel-arm-next/arch=arm,defconfig=kota2_defconfig,label=kernel_cloud/54/console
>>   https://ci.linaro.org/jenkins/job/khilman-kernel-arm-next/arch=arm,defconfig=marzen_defconfig,label=kernel_cloud/54/console
>> 
>> Kevin
>
> Hi Kevin,
>
> thanks for bringing that to my attention.
> I'll fix it up.

I imagine it's the same issue, but in updating the list of defconfigs to
build, I noticed this same error in bockw_defconfig:

https://ci.linaro.org/jenkins/job/khilman-kernel-arm-next/arch=arm,defconfig=bockw_defconfig,label=kernel_cloud/60/console

Kevin

      reply	other threads:[~2013-05-29 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 22:57 build failure: linux-next: ARM/SH-mobile defconfigs: kota2, marzen Kevin Hilman
2013-05-29  2:05 ` Simon Horman
2013-05-29 14:30   ` Kevin Hilman [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=877gihamfd.fsf@linaro.org \
    --to=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).