linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] imx/mx3: fix FTBFS for undefined symbols mx31_usbh1 and mx31_usbh2
Date: Mon, 21 Dec 2009 16:33:38 +0100	[thread overview]
Message-ID: <20091221153338.GB31014@pengutronix.de> (raw)
In-Reply-To: <4B2F8D50.60902@epfl.ch>

On Mon, Dec 21, 2009 at 03:59:28PM +0100, Valentin Longchamp wrote:
> Hallo Uwe,
>
> Uwe Kleine-K?nig wrote:
>> Use the symbols mxc_usbh1 and mxc_usbh2 introduced in
>>
>> 	c13a482 (MX3: Add USB platform devices and resources)
>>
>> instead.
>
> I have sent a patch to fix this. It was first sent on December, 4th and  
> again on December, 18th  
> (http://article.gmane.org/gmane.linux.ports.arm.kernel/71126)
OK, actually the patches are identically.  Sascha, you can interpret
this as an Acked-by: me.

Best regards
Uwe

-- 
Pengutronix e.K.                              | Uwe Kleine-K?nig            |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |

      reply	other threads:[~2009-12-21 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19 20:18 [PATCH 1/2] imx/mx3: fix FTBFS for undefined symbols mx31_usbh1 and mx31_usbh2 Uwe Kleine-König
2009-12-19 20:18 ` [PATCH 2/2] imx/mx3: depend on USB_ULPI for otg_ulpi_create Uwe Kleine-König
2009-12-21 15:25   ` Valentin Longchamp
2009-12-21 15:41     ` [PATCH v2] " Uwe Kleine-König
2009-12-22 16:31       ` [PATCH v3] " Uwe Kleine-König
2009-12-24 11:23         ` please pull FTBFS fixes (Was: [PATCH v3] imx/mx3: depend on USB_ULPI for otg_ulpi_create) Uwe Kleine-König
2009-12-21 14:59 ` [PATCH 1/2] imx/mx3: fix FTBFS for undefined symbols mx31_usbh1 and mx31_usbh2 Valentin Longchamp
2009-12-21 15:33   ` Uwe Kleine-König [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=20091221153338.GB31014@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;
as well as URLs for NNTP newsgroup(s).