From: Sekhar Nori <nsekhar@ti.com>
To: Paul Walmsley <paul@pwsan.com>, Roger Quadros <rogerq@ti.com>
Cc: <tony@atomide.com>, <rnayak@ti.com>, <nm@ti.com>, <kishon@ti.com>,
<george.cherian@ti.com>, <balbi@ti.com>, <balajitk@ti.com>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: DRA7: hwmod: Add OCP2SCP3 module
Date: Fri, 20 Jun 2014 16:50:15 +0530 [thread overview]
Message-ID: <53A418EF.5050005@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1406190546520.13869@utopia.booyaka.com>
On Thursday 19 June 2014 11:18 AM, Paul Walmsley wrote:
> On Wed, 18 Jun 2014, Roger Quadros wrote:
>
>> This module is needed for the SATA and PCIe PHYs.
>>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>> Tested-by: Roger Quadros <rogerq@ti.com>
>
> Is this one a fix? It looks to me like a new IP block addition.
This is not a regression fix, but this is the only thing preventing
users from using SATA on DRA7x - the DT fragments are already there.
Since its still early -rc cycle, I am hoping enabling support for new
devices can still go in.
Thanks,
Sekhar
next prev parent reply other threads:[~2014-06-20 11:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 12:16 [PATCH 0/2] ARM: DRA7: hwmod: fixes for 3.16 Roger Quadros
2014-06-18 12:16 ` [PATCH 1/2] ARM: DRA7: hwmod: Add OCP2SCP3 module Roger Quadros
2014-06-18 12:34 ` Rajendra Nayak
2014-06-18 19:49 ` Roger Quadros
2014-06-18 19:50 ` [PATCH v2 " Roger Quadros
2014-07-02 11:23 ` Roger Quadros
2014-07-03 8:20 ` Rajendra Nayak
2014-06-19 5:48 ` [PATCH " Paul Walmsley
2014-06-20 11:20 ` Sekhar Nori [this message]
2014-06-25 17:46 ` Kishon Vijay Abraham I
2014-06-26 9:39 ` Roger Quadros
2014-06-18 12:16 ` [PATCH 2/2] ARM: DRA7: hwmod: Fixup SATA hwmod Roger Quadros
2014-07-02 11:24 ` Roger Quadros
2014-07-03 8:27 ` Rajendra Nayak
2014-06-23 4:57 ` [PATCH 0/2] ARM: DRA7: hwmod: fixes for 3.16 Paul Walmsley
2014-06-23 14:46 ` Sekhar Nori
2014-06-23 16:34 ` Paul Walmsley
2014-06-24 5:05 ` Sekhar Nori
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=53A418EF.5050005@ti.com \
--to=nsekhar@ti.com \
--cc=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=george.cherian@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=rogerq@ti.com \
--cc=tony@atomide.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