From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM: mach-shmobile: mackerel: HDMI support
Date: Thu, 06 Jan 2011 03:11:16 +0000 [thread overview]
Message-ID: <20110106031116.GJ23889@linux-sh.org> (raw)
In-Reply-To: <w3pwrmjk2yu.wl%kuninori.morimoto.gx@renesas.com>
On Thu, Jan 06, 2011 at 09:51:14AM +0900, Kuninori Morimoto wrote:
> > Kuninori Morimoto (3):
> > ARM: mach-shmobile: mackerel: Add fsi_set_rate
> > ARM: mach-shmobile: mackerel: add HDMI video support
> > ARM: mach-shmobile: mackerel: Add HDMI sound support
> >
> > These are based on Paul's rmobile-latest branch (not mackerel branch)
>
> I'm so sorry.
> I noticed big mistake on these patches.
> Please drop it.
> And give me 2nd chance
>
Ok, I've taken the second version.
On Thu, Jan 06, 2011 at 11:43:00AM +0900, Kuninori Morimoto wrote:
> fsib_clk will be used when fdiv_clk failed on fsi_hdmi_set_rate.
And also applied this, thanks.
prev parent reply other threads:[~2011-01-06 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 11:24 [PATCH 0/3] ARM: mach-shmobile: mackerel: HDMI support Kuninori Morimoto
2011-01-06 0:51 ` Kuninori Morimoto
2011-01-06 3:11 ` Paul Mundt [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=20110106031116.GJ23889@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).