From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Tony Lindgren <tony@atomide.com>,
Sricharan R <r.sricharan@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
rnayak@ti.com, b-cousson@ti.com, t-kristo@ti.com, ambresh@ti.com
Subject: Re: [PATCH V2 14/14] ARM: OMAP4: hwmod data: Clean up the data file
Date: Fri, 7 Jun 2013 14:14:51 -0400 [thread overview]
Message-ID: <51B2231B.6060806@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306071807510.7753@utopia.booyaka.com>
On Friday 07 June 2013 02:10 PM, Paul Walmsley wrote:
> On Fri, 7 Jun 2013, Tony Lindgren wrote:
>
>> I had to undo the following parts to avoid regressions on omap4sdp.
>> Can you please follow up on fixing the related issues so the fixup
>> won't be needed?
>
> Well, I can't even test it at the moment. So it's probably best for
> Santosh and Sricharan to fix those issues - they're the ones who are
> responsible for testing the patch before it's sent. Unless there's
> some specific reason why I'd be the best person to do it?
>
Will take care of that Paul.
Regards,
Santosh
next prev parent reply other threads:[~2013-06-07 18:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 11:56 [PATCH V2 14/14] ARM: OMAP4: hwmod data: Clean up the data file Sricharan R
2013-06-07 12:32 ` Paul Walmsley
2013-06-07 16:29 ` Tony Lindgren
2013-06-07 17:50 ` Tony Lindgren
2013-06-07 18:10 ` Paul Walmsley
2013-06-07 18:14 ` Santosh Shilimkar [this message]
2013-06-07 18:37 ` Tony Lindgren
2013-06-07 18:14 ` Santosh Shilimkar
2013-06-07 18:37 ` Tony Lindgren
2013-06-07 18:44 ` Santosh Shilimkar
2013-06-08 16:46 ` Sricharan R
2013-06-08 16:57 ` Tony Lindgren
2013-06-08 17:21 ` Shilimkar, Santosh
2013-06-08 17:42 ` Tony Lindgren
2013-06-10 10:38 ` Tomi Valkeinen
2013-06-10 14:14 ` Tony Lindgren
2013-06-11 7:42 ` Tomi Valkeinen
2013-06-12 13:54 ` Tony Lindgren
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=51B2231B.6060806@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=ambresh@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=r.sricharan@ti.com \
--cc=rnayak@ti.com \
--cc=t-kristo@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;
as well as URLs for NNTP newsgroup(s).