linux-kernel - Re: [PATCH] clk: Make the managed clk functions generically available

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120918112555.GA21004@avionic-0098.mockup.avionic-design.de>
Date:	Tue, 18 Sep 2012 13:25:55 +0200
From:	Thierry Reding <thierry.reding@...onic-design.de>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Lars-Peter Clausen <lars@...afoo.de>,
	Greg Ungerer <gerg@...pgear.com>, dedekind1@...il.com,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Julia Lawall <julia.lawall@...6.fr>,
	linux-m68k@...ts.linux-m68k.org, Greg Ungerer <gerg@...inux.org>,
	linux-arm-kernel@...ts.infradead.org,
	Mike Turquette <mturquette@...com>
Subject: Re: [PATCH] clk: Make the managed clk functions generically available

On Tue, Sep 18, 2012 at 10:35:36AM +0100, Russell King - ARM Linux wrote:
> On Tue, Sep 18, 2012 at 10:00:37AM +0200, Thierry Reding wrote:
> > On Sat, Sep 15, 2012 at 10:31:52PM +0100, Russell King - ARM Linux wrote:
> > > On Wed, Sep 12, 2012 at 10:43:07PM +0200, Lars-Peter Clausen wrote:
> > > > I wouldn't mind having this merged sooner rather than later, there is at least
> > > > one driver in next which is currently broken due to the missing devm_clk_get.
> > > > Russell what's your plan for the patch? Maybe under the given circumstances it
> > > > makes sense to let it go through the m68k tree.
> > > 
> > > Ok, I've merged it but there was no indication in the patch that it was
> > > supposed to be a fix... there's no cc: to stable.  Does it need to go to
> > > stable?  When was this brokenness introduced?  What's the story for the
> > > m68k bit?
> > 
> > What tree is this supposed to go through? I've checked your ARM tree as
> > well as Mike's clock tree but neither seem to carry this patch. The
> > reason I ask is because I want to take a patch series that converts the
> > Unicore32 PWM code to the PWM framework into linux-next but it depends
> > on this patch as well.
> 
> It /is/ in my tree (you'll notice that it is in linux-next.)  You're
> probably looking at my Linaro tree instead, which doesn't carry
> anything which isn't about to be sent to Linus.

I must be blind then. next-20120918 doesn't have it. And looking at your
tree here[0] doesn't show the commit either.

> I'll publish the branch for this in the next couple of days.

Are you saying you haven't pushed the branch containing this commit to
your tree yet? That would certainly explain why I can't find it. Sorry
if I'm being dense.

I'll assume that it'll show up in linux-next eventually and that I can
push the dependent series as well.

Thierry

[0]: git://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-arm.git

Content of type "application/pgp-signature" skipped