From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "R, Sricharan" <r.sricharan@ti.com>,
Paul Walmsley <paul@pwsan.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Nayak, Rajendra" <rnayak@ti.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
"Kristo, Tero" <t-kristo@ti.com>, "K, Ambresh" <ambresh@ti.com>
Subject: Re: [PATCH V2 14/14] ARM: OMAP4: hwmod data: Clean up the data file
Date: Sat, 8 Jun 2013 10:42:42 -0700 [thread overview]
Message-ID: <20130608174241.GU3331@atomide.com> (raw)
In-Reply-To: <448912EABC71F84BBCADFD3C67C4BE52800C6F@DBDE04.ent.ti.com>
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [130608 10:27]:
> Sorry for top posting. We should still drop the IRQ data for those devices and only retain DMA data in that case.
OK
> Tony, can you please refresh your commit so that IRQ data is dropped from those devices ?
Additional patch please, I've already pushed it out.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 14/14] ARM: OMAP4: hwmod data: Clean up the data file
Date: Sat, 8 Jun 2013 10:42:42 -0700 [thread overview]
Message-ID: <20130608174241.GU3331@atomide.com> (raw)
In-Reply-To: <448912EABC71F84BBCADFD3C67C4BE52800C6F@DBDE04.ent.ti.com>
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [130608 10:27]:
> Sorry for top posting. We should still drop the IRQ data for those devices and only retain DMA data in that case.
OK
> Tony, can you please refresh your commit so that IRQ data is dropped from those devices ?
Additional patch please, I've already pushed it out.
Regards,
Tony
next prev parent reply other threads:[~2013-06-08 17:42 UTC|newest]
Thread overview: 36+ 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 11:56 ` Sricharan R
2013-06-07 12:32 ` Paul Walmsley
2013-06-07 12:32 ` Paul Walmsley
2013-06-07 16:29 ` Tony Lindgren
2013-06-07 16:29 ` Tony Lindgren
2013-06-07 17:50 ` Tony Lindgren
2013-06-07 17:50 ` Tony Lindgren
2013-06-07 18:10 ` Paul Walmsley
2013-06-07 18:10 ` Paul Walmsley
2013-06-07 18:14 ` Santosh Shilimkar
2013-06-07 18:14 ` Santosh Shilimkar
2013-06-07 18:37 ` Tony Lindgren
2013-06-07 18:37 ` Tony Lindgren
2013-06-07 18:14 ` Santosh Shilimkar
2013-06-07 18:14 ` Santosh Shilimkar
2013-06-07 18:37 ` Tony Lindgren
2013-06-07 18:37 ` Tony Lindgren
2013-06-07 18:44 ` Santosh Shilimkar
2013-06-07 18:44 ` Santosh Shilimkar
2013-06-08 16:46 ` Sricharan R
2013-06-08 16:46 ` Sricharan R
2013-06-08 16:57 ` Tony Lindgren
2013-06-08 16:57 ` Tony Lindgren
2013-06-08 17:21 ` Shilimkar, Santosh
2013-06-08 17:21 ` Shilimkar, Santosh
2013-06-08 17:42 ` Tony Lindgren [this message]
2013-06-08 17:42 ` Tony Lindgren
2013-06-10 10:38 ` Tomi Valkeinen
2013-06-10 10:38 ` Tomi Valkeinen
2013-06-10 14:14 ` Tony Lindgren
2013-06-10 14:14 ` Tony Lindgren
2013-06-11 7:42 ` Tomi Valkeinen
2013-06-11 7:42 ` Tomi Valkeinen
2013-06-12 13:54 ` Tony Lindgren
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=20130608174241.GU3331@atomide.com \
--to=tony@atomide.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=santosh.shilimkar@ti.com \
--cc=t-kristo@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 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.