From: tomeu.vizoso@collabora.com (Tomeu Vizoso)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v12 00/10] Per-user clock constraints
Date: Tue, 23 Sep 2014 09:40:12 +0200 [thread overview]
Message-ID: <542123DC.7060408@collabora.com> (raw)
In-Reply-To: <20140922150658.GM5182@n2100.arm.linux.org.uk>
On 09/22/2014 05:06 PM, Russell King - ARM Linux wrote:
> On Mon, Sep 22, 2014 at 04:12:02PM +0200, Tomeu Vizoso wrote:
>> Hello,
>>
>> my branch was finally processed by the 0day build farm and I have fixed the
>> three issues that came up:
>
> Patch 3 did not come through, so I can't see the changes there.
Yeah, I think all mailing lists choke on it because of its size and the
number of recipients, except linuxppc-dev:
http://patchwork.ozlabs.org/patch/391967/
You were on CC though.
> I'm
> assuming that there's some changes to clkdev in there which I need to
> see.
Nope, that one doesn't touch clkdev.
>> * export __clk_get and __clk_put, so they can be used by clock implementations
>> in modules that previously used clk_get and clk_put.
>
> This is something I'm not happy about. We don't want people getting
> access to these low level functions.
I see, will think something about it.
Thanks,
Tomeu
WARNING: multiple messages have this Message-ID (diff)
From: Tomeu Vizoso <tomeu.vizoso@collabora.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Mike Turquette <mturquette@linaro.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
linux-kernel@vger.kernel.org, tomasz.figa@gmail.com,
rabin@rab.in, Thierry Reding <thierry.reding@gmail.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v12 00/10] Per-user clock constraints
Date: Tue, 23 Sep 2014 09:40:12 +0200 [thread overview]
Message-ID: <542123DC.7060408@collabora.com> (raw)
In-Reply-To: <20140922150658.GM5182@n2100.arm.linux.org.uk>
On 09/22/2014 05:06 PM, Russell King - ARM Linux wrote:
> On Mon, Sep 22, 2014 at 04:12:02PM +0200, Tomeu Vizoso wrote:
>> Hello,
>>
>> my branch was finally processed by the 0day build farm and I have fixed the
>> three issues that came up:
>
> Patch 3 did not come through, so I can't see the changes there.
Yeah, I think all mailing lists choke on it because of its size and the
number of recipients, except linuxppc-dev:
http://patchwork.ozlabs.org/patch/391967/
You were on CC though.
> I'm
> assuming that there's some changes to clkdev in there which I need to
> see.
Nope, that one doesn't touch clkdev.
>> * export __clk_get and __clk_put, so they can be used by clock implementations
>> in modules that previously used clk_get and clk_put.
>
> This is something I'm not happy about. We don't want people getting
> access to these low level functions.
I see, will think something about it.
Thanks,
Tomeu
next prev parent reply other threads:[~2014-09-23 7:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 14:12 [PATCH v12 00/10] Per-user clock constraints Tomeu Vizoso
2014-09-22 14:12 ` Tomeu Vizoso
2014-09-22 14:12 ` [PATCH v12 01/10] clk: Export __clk_put and __clk_get so they can be used by modules Tomeu Vizoso
2014-09-22 14:12 ` Tomeu Vizoso
2014-09-22 14:12 ` [PATCH v12 02/10] clk: Add temporary mapping to the existing API Tomeu Vizoso
2014-09-22 14:12 ` Tomeu Vizoso
2014-09-22 14:13 ` [PATCH v12 03/10] clk: Move all drivers to use internal API Tomeu Vizoso
2014-09-22 14:13 ` Tomeu Vizoso
2014-09-22 14:15 ` [PATCH v12 04/10] clk: use struct clk only for external API Tomeu Vizoso
2014-09-22 14:15 ` Tomeu Vizoso
2014-09-22 14:15 ` [PATCH v12 05/10] clk: per-user clock accounting for debug Tomeu Vizoso
2014-09-22 14:15 ` Tomeu Vizoso
2014-09-22 14:15 ` [PATCH v12 06/10] clk: Add floor and ceiling constraints to clock rates Tomeu Vizoso
2014-09-22 14:15 ` Tomeu Vizoso
2014-09-22 14:15 ` [PATCH v12 07/10] clk: Warn of unbalanced clk_prepare() calls Tomeu Vizoso
2014-09-22 14:15 ` Tomeu Vizoso
2014-09-22 14:15 ` [PATCH v12 08/10] clk: Take the prepare lock when updating the list of per-user clks Tomeu Vizoso
2014-09-22 14:15 ` Tomeu Vizoso
2014-09-22 14:15 ` [PATCH v12 09/10] clk: Take the prepare lock when updating the per-user constraints Tomeu Vizoso
2014-09-22 14:15 ` Tomeu Vizoso
2014-09-22 14:15 ` [PATCH v12 10/10] clk: Add docs about calling clk_put after clk_get_parent Tomeu Vizoso
2014-09-22 14:15 ` Tomeu Vizoso
2014-09-22 18:08 ` [PATCH v12 04/10] clk: use struct clk only for external API Russell King - ARM Linux
2014-09-22 18:08 ` Russell King - ARM Linux
2014-09-23 9:09 ` Tomeu Vizoso
2014-09-23 9:09 ` Tomeu Vizoso
2014-09-22 15:06 ` [PATCH v12 00/10] Per-user clock constraints Russell King - ARM Linux
2014-09-22 15:06 ` Russell King - ARM Linux
2014-09-23 7:40 ` Tomeu Vizoso [this message]
2014-09-23 7:40 ` Tomeu Vizoso
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=542123DC.7060408@collabora.com \
--to=tomeu.vizoso@collabora.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 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.