From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: mythripk@ti.com
Cc: linux-omap@vger.kernel.org,
Ricardo Salveti de Araujo <ricardo.salveti@linaro.org>
Subject: Re: [PATCH v3 2/2] OMAPDSS: HDMI: Disable DDC internal pull up
Date: Tue, 20 Dec 2011 10:56:53 +0200 [thread overview]
Message-ID: <1324371413.2042.11.camel@deskari> (raw)
In-Reply-To: <1324370283-11884-2-git-send-email-mythripk@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
On Tue, 2011-12-20 at 14:08 +0530, mythripk@ti.com wrote:
> From: Mythri P K <mythripk@ti.com>
>
> Disables the internal pull resistor for SDA and SCL which are enabled by
> default, as there are external pull up's in 4460 and 4430 ES2.3
> SDP, Blaze and Panda Boards, It is done to avoid the EDID read failure.
>
> Signed-off-by: Ricardo Salveti de Araujo <ricardo.salveti@linaro.org>
> Signed-off-by: Mythri P K <mythripk@ti.com>
<snip>
> struct rfbi_timings {
> @@ -310,7 +314,7 @@ struct omap_dss_board_info {
> /* Init with the board info */
> extern int omap_display_init(struct omap_dss_board_info *board_data);
> /* HDMI mux init*/
> -extern int omap_hdmi_init(void);
> +extern int omap_hdmi_init(enum omap_hdmi_flags flags);
These patches you sent are broken. You add the omap_hdmi_init line in
the previous patch, and change it here, but the lines are different
(this one has two spaces between "int" and "omap_hdmi_init", and the
previous doesn't) so the patches cannot be applied.
I guess you hand edited them, or did something else manually. Never do
that. Use git rebase or similar methods to edit the patches, and create
the whole patch set with git-format-patch in one go.
If you absolutely have to edit the patch files, apply them to your git
tree afterwards and use git-format-patch to create the patch series
before sending.
And an introductory email with version history would be nice also.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-20 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 8:38 [PATCH v2 1/2] OMAPDSS: HDMI: Move duplicate code from boardfile mythripk
2011-12-20 8:38 ` [PATCH v3 2/2] OMAPDSS: HDMI: Disable DDC internal pull up mythripk
2011-12-20 8:56 ` Tomi Valkeinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-15 13:50 mythripk
2011-11-18 7:30 ` Tomi Valkeinen
2011-11-22 13:07 ` K, Mythri P
2011-11-22 13:19 ` 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=1324371413.2042.11.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mythripk@ti.com \
--cc=ricardo.salveti@linaro.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