[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190131132452.GD23791@localhost.localdomain>
Date: Thu, 31 Jan 2019 15:24:52 +0200
From: Matti Vaittinen <matti.vaittinen@...rohmeurope.com>
To: mazziesaccount@...il.com, corbet@....net, cw00.choi@...sung.com,
krzk@...nel.org, b.zolnierkie@...sung.com, mturquette@...libre.com,
sboyd@...nel.org, linux@...linux.org.uk, pombredanne@...b.com,
sre@...nel.org, vkoul@...nel.org, linux@...ck-us.net, pavel@....cz,
sjhuang@...vatar.ai, andrew.smirnov@...il.com,
djkurtz@...omium.org, akshu.agrawal@....com,
rafael.j.wysocki@...el.com, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v7 0/3] clk: clkdev add managed lookup registrations
Hello All,
On Fri, Dec 07, 2018 at 01:09:00PM +0200, Matti Vaittinen wrote:
> Series adds managed clkdev lookup interfaces and cleans few drivers
>
> Few clk drivers appear to be leaking clkdev lookup registrations at
> driver remove. The patch series adds devm versions of lookup
> registrations and cleans up few drivers. Driver clean-up patches have
> not been tested as I lack the HW. All testing and comments if
> driver/device removal is even possible for changed drivers is highly
> appreciated. If removal is not possible I will gladly drop the patches
> from series - although leaking lookups may serve as bad example for new
> developers =)
>
> Changed drivers are:
> clk-max77686 and clk-st
>
> Please note that the patch #2 requires this change to work correctly:
> https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/commit/?h=clk-next&id=05502bf9eb7a7297f5fa6f1d17b169b3d5b53570
I guess the dependency mentioned abowe is already in (most) of the
trees. (I can't say for sure as I don't know what is the correct tree
for clkdev - is it linux-arm.git as Russel is maintaining clkdev? If
yes, then the commit 05502bf9eb7a7297f5fa6f1d17b169b3d5b53570
"clk: of-provider: look at parent if registered device has no
provider info" seems to be sitting in maser branch).
So should I rebase this series to some other tree and resend? Or is this
something that is not wanted?
Br,
Matti Vaittinen
Powered by blists - more mailing lists