From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: mythripk@ti.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] OMAPDSS: HDMI: Interrupt and PHY state handling support
Date: Tue, 27 Mar 2012 13:29:49 +0300 [thread overview]
Message-ID: <1332844189.1867.109.camel@deskari> (raw)
In-Reply-To: <1332249307-26875-1-git-send-email-mythripk@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
On Tue, 2012-03-20 at 18:45 +0530, mythripk@ti.com wrote:
> From: Mythri P K <mythripk@ti.com>
>
> Add support for handling the DSS_HDMI interrupt in HDMI, A line that serves to
> notify HDMI of status change in PHY, PLL and CORE based on the registration.
> Also logic to support enabling of the PHY in TX_ON state only when a PHY_CONNECT
> which would make sure that TMDS lines are high before putting it in TX_ON state.
>
> Mythri P K (3):
> OMAPDSS: HDMI: support for interrupt enabling
> OMAPDSS: HDMI: Add support for DSS_HDMI Interrupt
> OMAPDSS: HDMI: wait for TMDS to be high before putting phy in TX_ON
Sorry, but this patch set is quite bad.
First of all, the subject on your third patch is again cut short. How do
you even do that? The subject seems to be fine above. I've never seen
other people do that, but you somehow manage to do it all the time. So,
please, read the git manual, fix your environment, your way of working,
or whatever is causing this so that we'll never see it again.
Then, the intro text above is rather confusing. Are there words missing
around the part with "PHY_CONNECT"? Please spend more time on the
descriptions, and possibly ask someone to proof-read them so that at
least there aren't words missing and they are somehow understandable.
I'll comment on other things in later mails.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-27 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 13:15 [PATCH 0/3] OMAPDSS: HDMI: Interrupt and PHY state handling support mythripk
2012-03-20 13:15 ` [PATCH 1/3] OMAPDSS: HDMI: support for interrupt enabling mythripk
2012-03-20 13:15 ` [PATCH 2/3] OMAPDSS: HDMI: Add support for DSS_HDMI Interrupt mythripk
2012-03-20 13:15 ` [PATCH 3/3] OMAPDSS: HDMI: wait for TMDS to be high before putting mythripk
2012-03-27 10:30 ` Tomi Valkeinen
2012-03-27 10:30 ` [PATCH 2/3] OMAPDSS: HDMI: Add support for DSS_HDMI Interrupt Tomi Valkeinen
2012-03-27 10:29 ` [PATCH 1/3] OMAPDSS: HDMI: support for interrupt enabling Tomi Valkeinen
2012-03-27 10:29 ` 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=1332844189.1867.109.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