All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: felipe.balbi@nokia.com
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] arm: omap1/2/3/4: convert clocksource to a platform_driver
Date: Tue, 06 Apr 2010 07:43:52 -0700	[thread overview]
Message-ID: <87hbnor68n.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100406063828.GP16297@nokia.com> (Felipe Balbi's message of "Tue\, 6 Apr 2010 09\:38\:28 +0300")

Felipe Balbi <felipe.balbi@nokia.com> writes:

> Hi,
>
> On Tue, Apr 06, 2010 at 12:57:16AM +0200, ext Kevin Hilman wrote:
>>What' you've created is not a generic clocksource driver but one that
>>can only work with the 32k sync timer.
>
> so I achieved my goal, which was to convert *32k-sync timer* into a
> platform_driver.

OK, then I misunderstood your goal.  Based on $SUBJECT, I thought
you were trying to create a generic clocksource driver.

Sorry for the confusion,

Kevin


  reply	other threads:[~2010-04-06 14:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 12:12 [PATCH] arm: omap1/2/3/4: convert clocksource to a platform_driver Felipe Balbi
2010-03-23 12:23 ` [PATCH v2] " Felipe Balbi
2010-03-23 13:29   ` [PATCH v3] " Felipe Balbi
2010-03-23 13:42     ` [PATCH] arm: omap1/2/3/4: change sync_32k_ick to ick Felipe Balbi
2010-03-23 18:07     ` [PATCH v3] arm: omap1/2/3/4: convert clocksource to a platform_driver Kevin Hilman
2010-03-24  6:34       ` Felipe Balbi
2010-03-24  6:54         ` Felipe Balbi
2010-03-26  7:21           ` [PATCH] " Felipe Balbi
2010-04-05 22:57             ` Kevin Hilman
2010-04-06  6:38               ` Felipe Balbi
2010-04-06 14:43                 ` Kevin Hilman [this message]
2010-04-06 15:26                   ` Felipe Balbi

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=87hbnor68n.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --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.