From: Tony Lindgren <tony@atomide.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: "Ujfalusi, Peter" <peter.ujfalusi@ti.com>,
Shubhrajyoti D <shubhrajyoti@ti.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: OMAP: DMA: Fix DMA channel end definition for OMAP36xx-PLUS devices
Date: Mon, 5 Mar 2012 14:22:16 -0800 [thread overview]
Message-ID: <20120305222216.GC12083@atomide.com> (raw)
In-Reply-To: <4F515529.1050005@ti.com>
* Jon Hunter <jon-hunter@ti.com> [120302 14:47]:
>
> Oops! I see that Peter has already fixed this one [1].
>
> Peter, looking at your fix it is good for OMAP4 but should we also
> fix for OMAP5 while we are at it? I checked and the register map is
> the same for OMAP5.
>
> Tony, I still think we should get rid of cpu_is_omap4430() altogether [2].
OK, makes sense. Applying [2] into fixes-non-critical-part2.
Thanks,
Tony
> [1] http://www.spinics.net/lists/linux-omap/msg65459.html
> [2] http://www.spinics.net/lists/linux-omap/msg65702.html
prev parent reply other threads:[~2012-03-05 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 1:10 [PATCH 1/2] ARM: OMAP: DMA: Fix DMA channel end definition for OMAP36xx-PLUS devices Jon Hunter
2012-03-02 23:18 ` Jon Hunter
2012-03-05 22:22 ` Tony Lindgren [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=20120305222216.GC12083@atomide.com \
--to=tony@atomide.com \
--cc=jon-hunter@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=shubhrajyoti@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;
as well as URLs for NNTP newsgroup(s).