From: Mike Turquette <mturquette@linaro.org>
To: Tomasz Figa <t.figa@samsung.com>
Cc: devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>,
Sachin Kamat <sachin.kamat@linaro.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
Lee Jones <lee.jones@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/8] clk: max77686: Clock provider implementation fixes
Date: Wed, 08 Jan 2014 08:31:38 -0800 [thread overview]
Message-ID: <20140108163138.27803.58310@quantum> (raw)
In-Reply-To: <2890647.PEOApIOYyP@amdc1227>
Quoting Tomasz Figa (2014-01-02 07:22:12)
> On Tuesday 31 of December 2013 11:42:15 Mike Turquette wrote:
> > Quoting Tomasz Figa (2013-12-12 08:07:13)
> > > This series intends to improve clock provider impementation of max77686
> > > PMIC driver. First two patches are simple fixes of current implementation
> > > to allow correct control of provided clocks. Further patches refactor
> > > the driver to make the code cleaner and prepare for further patches. Then
> > > last two patches add registration of OF clock provider and adjust device
> > > tree nodes of boards containing max77686 chip to contain properties
> > > required by clock provider.
> >
> > Acked-by: Mike Turquette <mturquette@linaro.org>
>
> Hmm... Shouldn't this series go through the clk tree directly? If not, who
> should be taking it?
Yes it should, but I guessed it would come in a pull request. Maybe Ack
is the wrong thing? I can just say "looks good to me me" or something
else.
Regards,
Mike
>
> Best regards,
> Tomasz
>
WARNING: multiple messages have this Message-ID (diff)
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/8] clk: max77686: Clock provider implementation fixes
Date: Wed, 08 Jan 2014 08:31:38 -0800 [thread overview]
Message-ID: <20140108163138.27803.58310@quantum> (raw)
In-Reply-To: <2890647.PEOApIOYyP@amdc1227>
Quoting Tomasz Figa (2014-01-02 07:22:12)
> On Tuesday 31 of December 2013 11:42:15 Mike Turquette wrote:
> > Quoting Tomasz Figa (2013-12-12 08:07:13)
> > > This series intends to improve clock provider impementation of max77686
> > > PMIC driver. First two patches are simple fixes of current implementation
> > > to allow correct control of provided clocks. Further patches refactor
> > > the driver to make the code cleaner and prepare for further patches. Then
> > > last two patches add registration of OF clock provider and adjust device
> > > tree nodes of boards containing max77686 chip to contain properties
> > > required by clock provider.
> >
> > Acked-by: Mike Turquette <mturquette@linaro.org>
>
> Hmm... Shouldn't this series go through the clk tree directly? If not, who
> should be taking it?
Yes it should, but I guessed it would come in a pull request. Maybe Ack
is the wrong thing? I can just say "looks good to me me" or something
else.
Regards,
Mike
>
> Best regards,
> Tomasz
>
next prev parent reply other threads:[~2014-01-08 16:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 16:07 [PATCH v2 0/8] clk: max77686: Clock provider implementation fixes Tomasz Figa
2013-12-12 16:07 ` Tomasz Figa
2013-12-12 16:07 ` [PATCH v2 1/8] clk: max77686: Correct callback used for checking clock status Tomasz Figa
2013-12-12 16:07 ` Tomasz Figa
2013-12-12 16:07 ` [PATCH v2 2/8] clk: max77686: Provide .recalc_rate() operation Tomasz Figa
2013-12-12 16:07 ` Tomasz Figa
2013-12-12 16:07 ` [PATCH v2 3/8] clk: max77686: Refactor successful exit of probe function Tomasz Figa
2013-12-12 16:07 ` Tomasz Figa
2013-12-12 16:07 ` [PATCH v2 5/8] clk: max77686: Fix clean-up in error and remove paths Tomasz Figa
2013-12-12 16:07 ` Tomasz Figa
[not found] ` <1386864441-19561-1-git-send-email-t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-12-12 16:07 ` [PATCH v2 4/8] clk: max77686: Make max77686_clk_register() return struct clk * Tomasz Figa
2013-12-12 16:07 ` Tomasz Figa
2013-12-12 16:07 ` [PATCH v2 6/8] clk: max77686: Refactor driver data handling Tomasz Figa
2013-12-12 16:07 ` Tomasz Figa
2013-12-12 16:07 ` [PATCH v2 7/8] clk: max77686: Register OF clock provider Tomasz Figa
2013-12-12 16:07 ` Tomasz Figa
2013-12-12 16:07 ` [PATCH v2 8/8] ARM: dts: Add clock provider specific properties to max77686 node Tomasz Figa
2013-12-12 16:07 ` Tomasz Figa
2013-12-30 17:41 ` [PATCH v2 0/8] clk: max77686: Clock provider implementation fixes Tomasz Figa
2013-12-30 17:41 ` Tomasz Figa
2013-12-31 19:42 ` Mike Turquette
2013-12-31 19:42 ` Mike Turquette
2014-01-02 15:22 ` Tomasz Figa
2014-01-02 15:22 ` Tomasz Figa
2014-01-06 11:06 ` Lee Jones
2014-01-06 11:06 ` Lee Jones
2014-01-08 16:31 ` Mike Turquette [this message]
2014-01-08 16:31 ` Mike Turquette
2014-01-08 16:44 ` Tomasz Figa
2014-01-08 16:44 ` Tomasz Figa
2014-01-08 17:01 ` Mike Turquette
2014-01-08 17:01 ` Mike Turquette
2014-01-08 17:15 ` Lee Jones
2014-01-08 17:15 ` Lee Jones
2014-01-08 17:59 ` Mike Turquette
2014-01-08 17:59 ` Mike Turquette
2014-01-08 18:04 ` Tomasz Figa
2014-01-08 18:04 ` Tomasz Figa
2014-01-08 21:54 ` Mike Turquette
2014-01-08 21:54 ` Mike Turquette
2014-01-08 22:03 ` Tomasz Figa
2014-01-08 22:03 ` Tomasz Figa
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=20140108163138.27803.58310@quantum \
--to=mturquette@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=sameo@linux.intel.com \
--cc=t.figa@samsung.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.