From: jgutierrez@ti.com (Gutierrez, Juan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] OMAP4: iommu: fix irq and clock name for dsp-iommu
Date: Mon, 7 May 2012 10:58:06 -0500 [thread overview]
Message-ID: <CADVn9REbqna7YHD2bDFyMCEmhfpbzWZ222fuOC2GxWUE705Lbg@mail.gmail.com> (raw)
In-Reply-To: <CAK=Wgbb8irgoyt21_tgqg+gFvKxSqs3Ud9KnTUkw-zMuE1X-wQ@mail.gmail.com>
Hi Ohad
On Sun, May 6, 2012 at 7:33 AM, Ohad Ben-Cohen <ohad@wizery.com> wrote:
> Hi Juan,
>
> On Sat, Apr 14, 2012 at 2:39 AM, Juan Gutierrez <jgutierrez@ti.com> wrote:
>> Irq and clock names were wrong for dsp iommu configuration
>> for omap4.
>
> Looks good.
>
>> Renamed tesla_ick to dsp_fck.
>
> If you're resubmitting the series, please indicate here why this
> change is needed (specifically let's mention commit 0e43327 "OMAP4:
> clock: Fix clock names and align with hwmod names").
>
Ok, I will mention the reason of this change in next series.
> Thanks,
> Ohad.
--
Thanks
juan gutierrez
next prev parent reply other threads:[~2012-05-07 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 23:39 [PATCH v2 0/3] Fixes in preparation for enabling Dsp in omap4 Juan Gutierrez
2012-04-13 23:39 ` [PATCH v2 1/3] omap: mailbox: enable mailbox irq per instance Juan Gutierrez
2012-05-06 16:00 ` Ohad Ben-Cohen
2012-05-07 22:09 ` Gutierrez, Juan
2012-05-08 9:43 ` Ohad Ben-Cohen
2012-04-13 23:39 ` [PATCH v2 2/3] OMAP4: iommu: fix irq and clock name for dsp-iommu Juan Gutierrez
2012-05-06 12:33 ` Ohad Ben-Cohen
2012-05-07 15:58 ` Gutierrez, Juan [this message]
2012-04-13 23:39 ` [PATCH v2 3/3] omap: remoteproc: add support for a boot register Juan Gutierrez
2012-05-06 11:21 ` Ohad Ben-Cohen
[not found] ` <CADVn9RFOBdw0_19ErT6qEpy7325TG7wWkDfJtdF-6jq74z3nFw@mail.gmail.com>
2012-05-07 15:05 ` Ohad Ben-Cohen
2012-05-07 15:54 ` Gutierrez, Juan
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=CADVn9REbqna7YHD2bDFyMCEmhfpbzWZ222fuOC2GxWUE705Lbg@mail.gmail.com \
--to=jgutierrez@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).