From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Guruswamy Senthilvadivu <svadivu@ti.com>
Cc: "hvaibhav@ti.com" <hvaibhav@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: Re: [PATCH v6 0/3] OMAP: DSS2: OMAPFB: Allow FB_OMAP2 to build
Date: Fri, 08 Oct 2010 09:52:23 +0000 [thread overview]
Message-ID: <1286531543.28499.1072.camel@tubuntu.research.nokia.com> (raw)
In-Reply-To: <1286520273-4892-1-git-send-email-svadivu@ti.com>
On Fri, 2010-10-08 at 08:44 +0200, ext Guruswamy Senthilvadivu wrote:
> From: Senthilvadivu Guruswamy <svadivu@ti.com>
>
> The changelog till v6 are:
> - Address Multi-omap build issue
> - Added a check to warn the wrong usage of vrfb
> in non-vrfb omap devices.
> - The patch subject is as per the naming conventions
> - patch 2/3 now has the changes in omap2/omapfb/Kconfig
> instead of omap2/Kconfig. The functional effect remains
> the same, and the place of implementation is more appropriate.
> - Provide details of non-vrfb devices in commit description in patch 3/3
> - Removed extra paranthesis in cpu checks
>
Thanks, looks fine to me. Applied to DSS2 tree.
Tomi
next prev parent reply other threads:[~2010-10-08 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 6:56 [PATCH v6 0/3] OMAP: DSS2: OMAPFB: Allow FB_OMAP2 to build without VRFB Guruswamy Senthilvadivu
2010-10-08 6:56 ` [PATCH v6 1/3] " Guruswamy Senthilvadivu
2010-10-08 6:56 ` [PATCH v6 2/3] OMAP: DSS2: OMAPFB: make VRFB depends on OMAP2,3 Guruswamy Senthilvadivu
2010-10-08 6:56 ` [PATCH v6 3/3] OMAP: DSS2: OMAPFB: Allow usage of def_vrfb only for omap2,3 Guruswamy Senthilvadivu
2010-10-08 9:52 ` Tomi Valkeinen [this message]
2010-10-08 10:31 ` [PATCH v6 0/3] OMAP: DSS2: OMAPFB: Allow FB_OMAP2 to build Guruswamy, Senthilvadivu
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=1286531543.28499.1072.camel@tubuntu.research.nokia.com \
--to=tomi.valkeinen@nokia.com \
--cc=hvaibhav@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=svadivu@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).