From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: Build failure on i.MX25 [Was: [PATCH] ARM: imx/mach-mx25_3ds: Use IMX_GPIO_NR instead of hard-coded values]
Date: Wed, 23 Feb 2011 00:36:10 +0100 [thread overview]
Message-ID: <20110222233610.GJ22310@pengutronix.de> (raw)
In-Reply-To: <1298417053-14418-1-git-send-email-fabio.estevam@freescale.com>
Hello Fabio,
as you currently seem to work on i.MX25: My mx25_defconfig our
autobuilder tests each night currently fails on latest linus/master.
You don't happen to already have looked into that?
(I don't have looked either, just want to prevent duplicated work.)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-02-22 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 23:24 [PATCH] ARM: imx/mach-mx25_3ds: Use IMX_GPIO_NR instead of hard-coded values Fabio Estevam
2011-02-22 23:36 ` Uwe Kleine-König [this message]
2011-02-22 23:56 ` Build failure on i.MX25 [Was: [PATCH] ARM: imx/mach-mx25_3ds: Use IMX_GPIO_NR instead of hard-coded values] Fabio Estevam
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=20110222233610.GJ22310@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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