linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>
Cc: "G, Manjunath Kondaiah" <manjugk@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v5 0/12] dmtimer adaptation to platform_driver
Date: Mon, 13 Dec 2010 18:09:39 -0800	[thread overview]
Message-ID: <87k4jd2jh8.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03736F5022@dbde02.ent.ti.com> (Tarun Kanti DebBarma's message of "Tue, 7 Dec 2010 10:29:19 +0530")

"DebBarma, Tarun Kanti" <tarun.kanti@ti.com> writes:

>> On Tue, Dec 07, 2010 at 05:14:07AM +0530, Tarun Kanti DebBarma wrote:
>> > dmtimer adaptation to platform_driver.
>> >
>> > This patch series is adaptation of dmtimer code to platform driver
>> > using omap_device and omap_hwmod abstraction.
>> >
>> > Tested on following platforms:
>> > OMAP4430, OMAP3430, OMAP3630, OMAP2430
>> > OMAP2420 -- Image with omap2plus_defconfig in too large to download on
>> N800.
>> 
>> How about omap1? The mainline code happily compiles and boots on osk5912
>> but this series is going to break omap1 build.
>
> I have built and booted on OMAP1 during v3. This time I could not because
> My OMAP1710 has gone bad. I am looking for one to test.
> That's precisely the reason I have not mentioned OMAP1. 

Rather than not mentioning OMAP1, you should state whether (or not) it
was tested on OMAP1.   As build/boot testing on OMAP1 is a requirement
for merge, this information is crucial.

Kevin



  reply	other threads:[~2010-12-14  2:09 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 23:44 [PATCH v5 0/12] dmtimer adaptation to platform_driver Tarun Kanti DebBarma
2010-12-06 16:28 ` G, Manjunath Kondaiah
2010-12-07  4:59   ` DebBarma, Tarun Kanti
2010-12-14  2:09     ` Kevin Hilman [this message]
2010-12-06 23:44 ` [PATCH v5 1/12] OMAP2+: dmtimer: add device names to flck nodes Tarun Kanti DebBarma
2010-12-06 23:44 ` [PATCH v5 2/12] OMAP2420: hwmod data: add dmtimer Tarun Kanti DebBarma
2010-12-06 16:57   ` G, Manjunath Kondaiah
2010-12-06 23:44 ` [PATCH v5 3/12] OMAP2430: " Tarun Kanti DebBarma
2010-12-06 23:44 ` [PATCH v5 4/12] OMAP3: " Tarun Kanti DebBarma
2010-12-06 23:44 ` [PATCH v5 5/12] OMAP4: " Tarun Kanti DebBarma
2010-12-06 23:44 ` [PATCH v5 6/12] OMAP: dmtimer: infrastructure to support hwmod Tarun Kanti DebBarma
2010-12-06 17:09   ` G, Manjunath Kondaiah
2010-12-07  4:50     ` DebBarma, Tarun Kanti
2010-12-06 23:44 ` [PATCH v5 7/12] OMAP1: dmtimer: conversion to platform devices Tarun Kanti DebBarma
2010-12-06 17:56   ` G, Manjunath Kondaiah
2010-12-07  5:17     ` DebBarma, Tarun Kanti
2010-12-06 23:44 ` [PATCH v5 8/12] OMAP2+: dmtimer: convert " Tarun Kanti DebBarma
2010-12-06 18:26   ` G, Manjunath Kondaiah
2010-12-07  5:21     ` DebBarma, Tarun Kanti
2010-12-07  5:46   ` Varadarajan, Charulatha
2010-12-07  5:50     ` DebBarma, Tarun Kanti
2010-12-06 23:44 ` [PATCH v5 9/12] OMAP: dmtimer: platform driver Tarun Kanti DebBarma
2010-12-06 19:10   ` G, Manjunath Kondaiah
2010-12-07  5:32     ` DebBarma, Tarun Kanti
2010-12-07  5:47       ` G, Manjunath Kondaiah
2010-12-07  6:14         ` DebBarma, Tarun Kanti
2010-12-06 23:44 ` [PATCH v5 10/12] OMAP: dmtimer: switch-over to platform device driver Tarun Kanti DebBarma
2010-12-07  5:27   ` Varadarajan, Charulatha
2010-12-07  5:49     ` DebBarma, Tarun Kanti
2010-12-13 15:07   ` Cousson, Benoit
2010-12-06 23:44 ` [PATCH v5 11/12] OMAP: dmtimer: pm_runtime support Tarun Kanti DebBarma
2010-12-06 23:44 ` [PATCH v5 12/12] OMAP: dmtimer: add timeout to low-level routines Tarun Kanti DebBarma
2010-12-14  6:45 ` [PATCH v5 0/12] dmtimer adaptation to platform_driver Paul Walmsley
2010-12-15  2:06 ` Kevin Hilman
2010-12-15  4:59   ` DebBarma, Tarun Kanti

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=87k4jd2jh8.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=manjugk@ti.com \
    --cc=tarun.kanti@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).