linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: i.MX27 clk: Separate DT and non-DT init procedure
Date: Mon, 9 Jun 2014 11:15:48 +0800	[thread overview]
Message-ID: <20140609031547.GZ8860@dragon> (raw)
In-Reply-To: <1402157366-25134-1-git-send-email-shc_work@mail.ru>

On Sat, Jun 07, 2014 at 08:09:25PM +0400, Alexander Shiyan wrote:
> This patch separates DT and non-DT clock initialization procedure,
> so we can avoid a lot of unneeded clk_register_clkdev() for DT case.
> 
> Signed-off-by: Alexander Shiyan <shc_work@mail.ru>

Applied both, thanks.

      parent reply	other threads:[~2014-06-09  3:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-07 16:09 [PATCH 1/2] ARM: i.MX27 clk: Separate DT and non-DT init procedure Alexander Shiyan
2014-06-07 16:09 ` [PATCH 2/2] ARM: i.MX27 clk: Use of_clk_init() for DT case Alexander Shiyan
2014-06-09  3:15 ` Shawn Guo [this message]

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=20140609031547.GZ8860@dragon \
    --to=shawn.guo@freescale.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 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).