From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [APPLIED] [PATCH 2/2] OMAP: Zoom2: Fix file system loading issue
Date: Wed, 17 Jun 2009 08:52:27 -0700 [thread overview]
Message-ID: <874ouezwlg.fsf@deeprootsystems.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608702F53D1877@dbde02.ent.ti.com> (Vikram Pandita's message of "Wed\, 17 Jun 2009 20\:49\:19 +0530")
"Pandita, Vikram" <vikram.pandita@ti.com> writes:
>>This patch has been applied to the linux-omap
>>by youw fwiendly patch wobot.
>>
>>Branch in linux-omap: omap-fixes
>>
>>Initial commit ID (Likely to change): f84eca35d44fd64cdde542f12d08eb04ca534954
>>
>>PatchWorks
>>http://patchwork.kernel.org/patch/29668/
>
> This patch breaks the zoom2 build.
> ...
> arch/arm/mach-omap2/board-zoom-debugboard.c:87: error: 'UPF_IRQ_TRIG_HIGH' undeclared here (not in a function)
> make[1]: *** [arch/arm/mach-omap2/board-zoom-debugboard.o] Error 1
> make: *** [arch/arm/mach-omap2] Error 2
> ...
>
> There is a dependency on 8250 patch:
> http://lists.arm.linux.org.uk/lurker/attach/1@20090612.173251.776f9eda.attach
>
>
> how do you want to address this issue?
>
Tony,
IMO, We should probably stage the 8250 UPF_* change in l-o as well
while we wait for the linux-serial lag.
Kevin
next prev parent reply other threads:[~2009-06-17 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 0:49 [PATCH 2/2] OMAP: Zoom2: Fix file system loading issue Vikram Pandita
2009-06-17 13:57 ` [APPLIED] " Tony Lindgren
2009-06-17 15:19 ` Pandita, Vikram
2009-06-17 15:52 ` Kevin Hilman [this message]
2009-06-17 15:54 ` Kevin Hilman
2009-06-17 16:26 ` Pandita, Vikram
2009-06-18 5:27 ` Tony Lindgren
2009-06-18 13:32 ` Pandita, Vikram
2009-06-18 17:38 ` Kevin Hilman
2009-06-18 14:11 ` Kevin Hilman
2009-06-22 12:43 ` Tony Lindgren
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=874ouezwlg.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=vikram.pandita@ti.com \
/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