From: Mugunthan V N <mugunthanvnm@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/1] ARM: OMAP2+: DRA7: hwmod: Add hwmod data for MDIO and CPSW
Date: Tue, 29 Oct 2013 14:46:40 +0530 [thread overview]
Message-ID: <526F7CF8.4070406@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1310191745390.12900@utopia.booyaka.com>
On Saturday 19 October 2013 11:15 PM, Paul Walmsley wrote:
> On Fri, 18 Oct 2013, Mugunthan V N wrote:
>
>> > Adding hwmod data for CPSW and MDIO which is present in DRA7xx SoC
>> >
>> > Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
> Has a DRA7xx public TRM been published yet?
Paul
There is no TRM available publically as of now, it may take another a
month time.
Regards
Mugunthan V N
WARNING: multiple messages have this Message-ID (diff)
From: mugunthanvnm@ti.com (Mugunthan V N)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/1] ARM: OMAP2+: DRA7: hwmod: Add hwmod data for MDIO and CPSW
Date: Tue, 29 Oct 2013 14:46:40 +0530 [thread overview]
Message-ID: <526F7CF8.4070406@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1310191745390.12900@utopia.booyaka.com>
On Saturday 19 October 2013 11:15 PM, Paul Walmsley wrote:
> On Fri, 18 Oct 2013, Mugunthan V N wrote:
>
>> > Adding hwmod data for CPSW and MDIO which is present in DRA7xx SoC
>> >
>> > Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
> Has a DRA7xx public TRM been published yet?
Paul
There is no TRM available publically as of now, it may take another a
month time.
Regards
Mugunthan V N
next prev parent reply other threads:[~2013-10-29 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 14:51 [PATCH v2 1/1] ARM: OMAP2+: DRA7: hwmod: Add hwmod data for MDIO and CPSW Mugunthan V N
2013-10-18 14:51 ` Mugunthan V N
2013-10-19 17:45 ` Paul Walmsley
2013-10-19 17:45 ` Paul Walmsley
2013-10-29 9:16 ` Mugunthan V N [this message]
2013-10-29 9:16 ` Mugunthan V N
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=526F7CF8.4070406@ti.com \
--to=mugunthanvnm@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.