public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: u8500_defconfig: build failure in linux-next
Date: Fri, 17 May 2013 07:01:26 -0700	[thread overview]
Message-ID: <87bo89u2mh.fsf@linaro.org> (raw)
In-Reply-To: <CACRpkdYLskC67vXQsVq470yo5J+E6eLtPz5-em4Qd_Pe0pwJiA@mail.gmail.com> (Linus Walleij's message of "Fri, 17 May 2013 08:31:31 +0200")

Linus Walleij <linus.walleij@linaro•org> writes:

> On Thu, May 16, 2013 at 1:29 AM, Kevin Hilman <khilman@linaro•org> wrote:
>
>> Lee, Linus,
>>
>> In building all the ARM defconfigs in linux-next, I noticed
>> u8500_defconfig not building:
>>
>>   [...]
>>   CC      drivers/mfd/ab8500-debugfs.o
>> /work/kernel/next/drivers/mfd/ab8500-debugfs.c:95:23: fatal error:
>> mach/irqs.h: No such file or directory
>>
>> Same build error on v3.10-rc1 and Linus' master branch (but is fine on v3.9)
>
> Yes, I sent this patch:
> http://marc.info/?l=linux-kernel&m=136601206705342&w=2

Great.

> Sam's been a bit overloaded that is why it's taking time to reach
> Torvalds tree. Recently Lee started to help out queueing patches
> for MFD so hopefully the bottleneck will be solved this way.

Looks like this hit linux-next today, so u8500_defconfig is back to
building cleanly in linux-next.

Thanks,

Kevin

      reply	other threads:[~2013-05-17 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 23:29 u8500_defconfig: build failure in linux-next Kevin Hilman
2013-05-17  6:31 ` Linus Walleij
2013-05-17 14:01   ` 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=87bo89u2mh.fsf@linaro.org \
    --to=khilman@linaro$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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