From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH resend] omap: Fix linker error in drivers/video/omap/lcd_2430sdp.c
Date: Mon, 28 Feb 2011 17:39:28 -0800 [thread overview]
Message-ID: <20110301013928.GL20560@atomide.com> (raw)
In-Reply-To: <1298905757.9809.135.camel@deskari>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [110228 07:07]:
>
> Well, it's a bit ugly, but I'm fine with it. It's for the old omapfb,
> which hopefully nobody uses anymore (right =), and there's no simple way
> to make it modular and neat.
How about let's make mach-omap2 boards all use the new code?
That way the old code can be omap1 only.
Regards,
Tony
next prev parent reply other threads:[~2011-03-01 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1298193466-29534-1-git-send-email-jhnikula@gmail.com>
2011-02-20 20:04 ` [PATCH resend] omap: Fix linker error in drivers/video/omap/lcd_2430sdp.c Jarkko Nikula
2011-02-24 21:26 ` Tony Lindgren
2011-02-28 14:47 ` Jarkko Nikula
2011-02-28 15:09 ` Tomi Valkeinen
2011-03-01 1:39 ` Tony Lindgren [this message]
2011-03-01 6:29 ` Tomi Valkeinen
2011-03-02 17:36 ` 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=20110301013928.GL20560@atomide.com \
--to=tony@atomide.com \
--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).