From: sylvester.nawrocki@gmail.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v7 1/5] omap3isp: Modify clocks registration to avoid circular references
Date: Tue, 31 Dec 2013 22:23:26 +0100 [thread overview]
Message-ID: <52C335CE.8000603@gmail.com> (raw)
In-Reply-To: <20131231193707.12054.68169@quantum>
On 12/31/2013 08:37 PM, Mike Turquette wrote:
> Quoting Mike Turquette (2013-12-19 00:07:29)
>> Quoting Sylwester Nawrocki (2013-12-16 14:14:37)
>>> Hi Mike,
>>>
>>> Laurent has already taken this patch into his tree, could you apply
>>> the remaining ones to your clk tree so this series has enough exposure
>>> in -next ?
>>
>> I've taken this in privately to do a little testing. If all goes well
>> then I'll push it out to clk-next very soon.
>
> This is in clk-next now. Hopefully nothing bad will happen when it hits
> linux-next ;-)
Thanks Mike. Yes, fingers crossed ;)
Regards,
Sylwester
next prev parent reply other threads:[~2013-12-31 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 17:12 [RESEND PATCH v7 0/5] clk: clock deregistration support Sylwester Nawrocki
2013-12-04 17:12 ` [RESEND PATCH v7 1/5] omap3isp: Modify clocks registration to avoid circular references Sylwester Nawrocki
2013-12-16 22:14 ` Sylwester Nawrocki
2013-12-19 8:07 ` Mike Turquette
2013-12-31 19:37 ` Mike Turquette
2013-12-31 21:23 ` Sylwester Nawrocki [this message]
2013-12-04 17:12 ` [RESEND PATCH v7 2/5] clk: Provide not locked variant of of_clk_get_from_provider() Sylwester Nawrocki
2013-12-04 17:12 ` [RESEND PATCH v7 3/5] clkdev: Fix race condition in clock lookup from device tree Sylwester Nawrocki
2013-12-04 17:12 ` [RESEND PATCH v7 4/5] clk: Add common __clk_get(), __clk_put() implementations Sylwester Nawrocki
2013-12-04 17:12 ` [RESEND PATCH v7 5/5] clk: Implement clk_unregister Sylwester Nawrocki
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=52C335CE.8000603@gmail.com \
--to=sylvester.nawrocki@gmail.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).