From: valentin.longchamp@epfl.ch (Valentin Longchamp)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mx31moboard: fix typo
Date: Fri, 04 Dec 2009 09:39:35 +0100 [thread overview]
Message-ID: <4B18CAC7.30907@epfl.ch> (raw)
In-Reply-To: <20091203193321.GE22533@pengutronix.de>
Robert Schwebel wrote:
> On Thu, Dec 03, 2009 at 08:30:34PM +0100, Robert Schwebel wrote:
>> Currently, linux-next breaks due to a typo introduced in commit
>> 33c4d91928bea4444b067e620496befbeb87029c
>>
>> This patch fixes it.
Thanks for fixing the typo, I gave me one warning that I had never noticed.
>
> But something else must be missing, I still get this:
>
> arch/arm/mach-mx3/mx31moboard.c: In function 'moboard_usbh2_init':
> arch/arm/mach-mx3/mx31moboard.c:395: error: 'mx31_usbh2' undeclared (first use in this function)
> arch/arm/mach-mx3/mx31moboard.c:395: error: (Each undeclared identifier is reported only once
> arch/arm/mach-mx3/mx31moboard.c:395: error: for each function it appears in.)
> make[1]: *** [arch/arm/mach-mx3/mx31moboard.o] Error 1
>
This comes from the usb host support for mx31 that should come with
2.6.33. Does linux-next already include these patches ?
Val
--
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp at epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne
next prev parent reply other threads:[~2009-12-04 8:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 19:30 [PATCH] mx31moboard: fix typo Robert Schwebel
2009-12-03 19:33 ` Robert Schwebel
2009-12-04 8:39 ` Valentin Longchamp [this message]
2009-12-04 11:14 ` Valentin Longchamp
2009-12-04 12:20 ` Sascha Hauer
2009-12-04 15:50 ` [PATCH 1/1] mx31moboard: fix usbh device names Valentin Longchamp
2009-12-04 9:14 ` [PATCH] mx31moboard: fix typo Guennadi Liakhovetski
2009-12-04 17:30 ` Valentin Longchamp
2009-12-04 17:46 ` Daniel Mack
2009-12-09 12:44 ` Valentin Longchamp
2009-12-09 13:57 ` Daniel Mack
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=4B18CAC7.30907@epfl.ch \
--to=valentin.longchamp@epfl.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.