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 13:54:32 -0800 [thread overview]
Message-ID: <20140108215432.27803.3120@quantum> (raw)
In-Reply-To: <4160932.uvjJSNcuKL@amdc1227>
Quoting Tomasz Figa (2014-01-08 10:04:57)
> On Wednesday 08 of January 2014 09:59:39 Mike Turquette wrote:
> > Quoting Lee Jones (2014-01-08 09:15:44)
> > > > I believe Lee has already applied this one, but in future, to avoid such
> > > > confusion, if it's more convenient for you, I can send you any clock
> > > > series as pull requests.
> > >
> > > Me? I haven't applied any clk patches.
> >
> > I have taken patches 1-7 into clk-next just now.
>
> Thanks.
>
> > I can take patch #8 as
> > well but it would probably be better to send it through arm-soc?
>
> Hmm, patch 8 is trivial enough to not cause any merge conflicts, but since
> it's unlikely that any users depending on introduced changes will show up
> for 3.14 it shouldn't really matter which tree it goes through...
In the absence of any strong opinion on the topic I have taken patch #8
into clk-next for 3.14.
Regards,
Mike
>
> Best regards,
> Tomasz
>
next prev parent reply other threads:[~2014-01-08 21:54 UTC|newest]
Thread overview: 21+ 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 ` [PATCH v2 1/8] clk: max77686: Correct callback used for checking clock status Tomasz Figa
2013-12-12 16:07 ` [PATCH v2 2/8] clk: max77686: Provide .recalc_rate() operation Tomasz Figa
2013-12-12 16:07 ` [PATCH v2 3/8] clk: max77686: Refactor successful exit of probe function 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 ` [PATCH v2 6/8] clk: max77686: Refactor driver data handling 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 ` [PATCH v2 7/8] clk: max77686: Register OF clock provider 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-30 17:41 ` [PATCH v2 0/8] clk: max77686: Clock provider implementation fixes Tomasz Figa
2013-12-31 19:42 ` Mike Turquette
2014-01-02 15:22 ` Tomasz Figa
2014-01-06 11:06 ` Lee Jones
2014-01-08 16:31 ` Mike Turquette
2014-01-08 16:44 ` Tomasz Figa
2014-01-08 17:01 ` Mike Turquette
2014-01-08 17:15 ` Lee Jones
2014-01-08 17:59 ` Mike Turquette
2014-01-08 18:04 ` Tomasz Figa
2014-01-08 21:54 ` Mike Turquette [this message]
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=20140108215432.27803.3120@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 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).