From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: mythripk@ti.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v4 0/4] OMAPDSS: HDMI: Improve the timings logic in HDMI
Date: Mon, 09 Jan 2012 09:01:17 +0200 [thread overview]
Message-ID: <1326092477.1900.12.camel@deskari> (raw)
In-Reply-To: <1325852530-4829-1-git-send-email-mythripk@ti.com>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
On Fri, 2012-01-06 at 17:52 +0530, mythripk@ti.com wrote:
> From: Mythri P K <mythripk@ti.com>
>
> There are some duplicate timing structure which are not needed thus removing
> them to clean the code.
> Also the static mapped timing structure is quite complicated to add new
> timings, so simplify it by using array indexed method.
>
> changes since v3: Remove double call of function
> changes since v2: Incorporate changes in find_timing function
> changes since V1: change of hdmi_find_timing function to return pointer to the
> timing struct rather than deep copy to timing structure passed as parameter
> variable name change from temp to timing2 in comparator function.
This patch set looks fine now, thanks. I'll apply to dss tree.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-01-09 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 12:22 [PATCH v4 0/4] OMAPDSS: HDMI: Improve the timings logic in HDMI mythripk
2012-01-06 12:22 ` [PATCH v4 1/4] OMAPDSS: HDMI: remove duplicate video interface code mythripk
2012-01-06 12:22 ` [PATCH v4 2/4] OMAPDSS: HDMI: update static timing table mythripk
2012-01-06 12:22 ` [PATCH v4 3/4] OMAPDSS: HDMI: change the timing match logic mythripk
2012-01-06 12:22 ` [PATCH v4 4/4] OMAPDSS: HDMI: remove duplicate code and mode parameter mythripk
2012-01-09 7:01 ` Tomi Valkeinen [this message]
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=1326092477.1900.12.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mythripk@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