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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 18 Sep 2012 10:35:36 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Thierry Reding <thierry.reding@...onic-design.de>
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: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'll publish the
branch for this in the next couple of days.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists