linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Emil Medve <Emilian.Medve@Freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org, haokexin@gmail.com,
	Mike Turquette <mturquette@linaro.org>,
	yuantian.tang@Freescale.com
Subject: Re: [PATCH v2 00/10] clk: qoriq: Add support for the FMan clock
Date: Wed, 28 Jan 2015 16:59:43 -0600	[thread overview]
Message-ID: <1422485983.10544.97.camel@freescale.com> (raw)
In-Reply-To: <54C95910.60402@Freescale.com>

On Wed, 2015-01-28 at 15:48 -0600, Emil Medve wrote:
> Hello Mike,
> 
> 
> On 01/28/2015 12:15 PM, Mike Turquette wrote:
> > Quoting Emil Medve (2015-01-21 02:03:22)
> >> Based on clk-next from git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
> >>
> >> v2:     Rebased as several prerequisite patches (including a file rename) got
> >>         applied upstream
> >>
> >> Emil Medve (9):
> >>   clk: qoriq: Fix checkpatch type PARENTHESIS_ALIGNMENT
> >>   clk: qoriq: Fix checkpatch type ALLOC_WITH_MULTIPLY
> >>   clk: qoriq: Fix checkpatch type ALLOC_SIZEOF_STRUCT
> >>   clk: qoriq: Fix checkpatch type OOM_MESSAGE
> >>   clk: qoriq: Make local symbol 'static'
> >>   clk: qoriq: Replace kzalloc() with kmalloc()
> >>   clk: qoriq: Use pr_fmt()
> > 
> > Patches 1-7 applied to clk-next towards 3.20
> 
> Thank you
> 
> > I'd prefer some
> > reviewed-by's from your peers at freescale for the clock driver
> > correctness.
> 
> That's fair
> 
> >>   powerpc/corenet: Enable CLK_QORIQ
> 
> I was thinking Scott can pick this up

Not if the patch that introduces CLK_QORIQ goes in via another tree.

> >> Igal Liberman (1):
> >>   clk: qoriq: Add support for the FMan clock
> 
> Scott, I'd appreciate your help here

>From internal discussion I believe you have some comments of your own on
this patch...

-Scott

      reply	other threads:[~2015-01-28 22:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 10:03 [PATCH v2 00/10] clk: qoriq: Add support for the FMan clock Emil Medve
2015-01-21 10:03 ` [PATCH v2 01/10] clk: qoriq: Fix checkpatch type PARENTHESIS_ALIGNMENT Emil Medve
2015-01-21 10:03 ` [PATCH v2 02/10] clk: qoriq: Fix checkpatch type ALLOC_WITH_MULTIPLY Emil Medve
2015-01-21 10:03 ` [PATCH v2 03/10] clk: qoriq: Fix checkpatch type ALLOC_SIZEOF_STRUCT Emil Medve
2015-01-21 10:03 ` [PATCH v2 04/10] clk: qoriq: Fix checkpatch type OOM_MESSAGE Emil Medve
2015-01-21 10:03 ` [PATCH v2 05/10] clk: qoriq: Make local symbol 'static' Emil Medve
2015-01-21 10:03 ` [PATCH v2 06/10] clk: qoriq: Replace kzalloc() with kmalloc() Emil Medve
2015-01-21 10:03 ` [PATCH v2 07/10] clk: qoriq: Use pr_fmt() Emil Medve
2015-01-21 10:03 ` [PATCH v2 08/10] powerpc/corenet: Enable CLK_QORIQ Emil Medve
2015-02-04  2:54   ` Yuantian Tang
2015-01-21 10:03 ` [PATCH v2 09/10] clk: qoriq: Add support for the platform PLL Emil Medve
2015-01-29  2:26   ` Yuantian Tang
2015-01-28 18:15 ` [PATCH v2 00/10] clk: qoriq: Add support for the FMan clock Mike Turquette
2015-01-28 21:48   ` Emil Medve
2015-01-28 22:59     ` Scott Wood [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=1422485983.10544.97.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=Emilian.Medve@Freescale.com \
    --cc=haokexin@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mturquette@linaro.org \
    --cc=yuantian.tang@Freescale.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).