All of lore.kernel.org
 help / color / mirror / Atom feed
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Consolidate clks_register() and similar
Date: Mon, 11 Jan 2010 14:06:08 -0800	[thread overview]
Message-ID: <87my0kmh4f.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100110172825.GB8639@n2100.arm.linux.org.uk> (Russell King's message of "Sun\, 10 Jan 2010 17\:28\:25 +0000")

Russell King - ARM Linux <linux@arm.linux.org.uk> writes:

> Most machine classes want some way to register a block of clk_lookup
> structures, and most do it by implementing a clks_register() type
> function which walks an array, or by open-coding a loop.
>
> Consolidate all this into clkdev_add_table().
>
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>

Reviewed-by: Kevin Hilman <khilman@deeprootsystems.com>

Are you planning this for 2.6.33-rc?  or 2.6.34?

> ---
> This misses out Davinci, which needs cleaning up to remove its
> seemingly redundant wrapping of the clk_lookup structure.

This should take care of davinci.  Tested on v2.6.33-rc3 + $SUBJECT patch.

  parent reply	other threads:[~2010-01-11 22:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 17:28 [PATCH] Consolidate clks_register() and similar Russell King - ARM Linux
2010-01-10 22:23 ` Jeremy Kerr
2010-01-10 23:12   ` Russell King - ARM Linux
2010-01-11  1:04     ` Ben Dooks
2010-01-11 17:26 ` H Hartley Sweeten
2010-01-11 17:28   ` Russell King - ARM Linux
2010-01-11 22:06 ` Kevin Hilman [this message]
2010-01-12 12:17   ` Russell King - ARM Linux
2010-01-12 17:29     ` H Hartley Sweeten
2010-01-12 17:35       ` Russell King - ARM Linux
2010-01-12 17:43         ` H Hartley Sweeten
2010-01-12 18:57           ` Russell King - ARM Linux
2010-01-12 19:16     ` Kevin Hilman
2010-01-12  0:11 ` Eric Miao

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=87my0kmh4f.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.