From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org, archit@ti.com
Subject: Re: [PATCHv3 0/5] OMAP: VRFB: convert to platform device
Date: Wed, 17 Oct 2012 18:29:26 +0000 [thread overview]
Message-ID: <20121017182926.GW15569@atomide.com> (raw)
In-Reply-To: <507E87B7.3070707@ti.com>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [121017 03:27]:
> Hi Tony,
>
> I have pushed this vrfb series and the omapdss version series to:
>
> git://gitorious.org/linux-omap-dss2/linux.git 3.8/dss-version
I used this branch up to commit 35f70935c64ae229ebd1fc65398ec68d4d803712,
but left out the x86 compile changes as those seem unrelated to the plat
issue.
> git://gitorious.org/linux-omap-dss2/linux.git 3.8/vrfb-conversion
And then I merged in this branch. I have the merged branch at
omap-for-v3.8/cleanup-headers-dss.
> If they look ok to you and we don't get any other comments, I think
> these branches can be considered stable and you can pull them.
Thanks yes let's consider those frozen and if something needs to
be fixed it should be done on top of those commits.
> After these are merged:
>
> $ git grep -E "(plat/)|(mach/)" drivers/video/omap2/
> drivers/video/omap2/omapfb/omapfb-ioctl.c:#include <plat/vram.h>
> drivers/video/omap2/omapfb/omapfb-main.c:#include <plat/vram.h>
> drivers/video/omap2/vram.c:#include <plat/vram.h>
>
> So the vram stuff should be the only omap dependency left in omapdss and
> omapfb. I'll start working on that soon.
OK thanks a lot. Then there's also the two vout files that
you may already have patches for:
drivers/media/platform/omap/omap_vout.c
drivers/media/platform/omap/omap_voutlib.c
Regards,
Tony
next prev parent reply other threads:[~2012-10-17 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 10:18 [PATCHv3 0/5] OMAP: VRFB: convert to platform device Tomi Valkeinen
2012-10-17 10:18 ` [PATCHv3 1/5] OMAP: VRFB: convert vrfb " Tomi Valkeinen
2012-10-17 10:18 ` [PATCHv3 2/5] OMAP: move arch/arm/plat-omap/include/plat/vrfb.h Tomi Valkeinen
2012-10-17 10:18 ` [PATCHv3 3/5] OMAP: SDRC: remove VRFB code Tomi Valkeinen
2012-10-17 10:18 ` [PATCHv3 4/5] OMAPDSS: VRFB: add omap_vrfb_supported() Tomi Valkeinen
2012-10-17 10:18 ` [PATCHv3 5/5] OMAPFB: use omap_vrfb_supported() Tomi Valkeinen
2012-10-17 10:25 ` [PATCHv3 0/5] OMAP: VRFB: convert to platform device Tomi Valkeinen
2012-10-17 18:29 ` Tony Lindgren [this message]
2012-10-18 12:45 ` Tomi Valkeinen
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=20121017182926.GW15569@atomide.com \
--to=tony@atomide.com \
--cc=archit@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@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;
as well as URLs for NNTP newsgroup(s).