From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: build failure: linux-next: ARM defconfigs: imx_v4_v5, imx_v6_v7
Date: Thu, 30 May 2013 16:41:12 -0600 [thread overview]
Message-ID: <51A7D588.1070605@wwwdotorg.org> (raw)
In-Reply-To: <87fvx43xpd.fsf@linaro.org>
On 05/30/2013 04:33 PM, Kevin Hilman wrote:
> Hello,
>
> The SPI driver for IMX started failing in linux-next (next-20130530)
> where the previous tag build fine. Below is the build error[1],
> followed by the the commit[2] that I think introduced the problem. It
> appears to be some missing (or extra) curly braces.
Sorry about that. Sachin Kamat <sachin.kamat@linaro.org> has already
sent a patch, which Mark has applied, so this should be fixed in the
next linux-next. Unfortunately, linux-spi at vger.kernel.org doesn't seem
to be archived anywhere, so I can't link to it. Oh, I guess gitweb has it:
https://git.kernel.org/cgit/linux/kernel/git/broonie/spi.git/commit/?h=topic/bpw&id=6051426fd0538eac4e28c55a08e4f4fb1c709b65
prev parent reply other threads:[~2013-05-30 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 22:33 build failure: linux-next: ARM defconfigs: imx_v4_v5, imx_v6_v7 Kevin Hilman
2013-05-30 22:41 ` Stephen Warren [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=51A7D588.1070605@wwwdotorg.org \
--to=swarren@wwwdotorg.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