linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@avionic-design.de>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Greg Ungerer <gerg@snapgear.com>,
	dedekind1@gmail.com,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Julia Lawall <julia.lawall@lip6.fr>,
	linux-m68k@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>,
	linux-arm-kernel@lists.infradead.org,
	Mike Turquette <mturquette@ti.com>
Subject: Re: [PATCH] clk: Make the managed clk functions generically available
Date: Tue, 18 Sep 2012 13:25:55 +0200	[thread overview]
Message-ID: <20120918112555.GA21004@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <20120918093536.GV12245@n2100.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-09-18 11:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09 15:01 [PATCH] clk: Make the managed clk functions generically available Lars-Peter Clausen
2012-09-09 20:57 ` Russell King - ARM Linux
2012-09-09 23:50 ` Mark Brown
2012-09-10  0:15   ` Russell King - ARM Linux
2012-09-10  0:20     ` Mark Brown
2012-09-10  0:39       ` Russell King - ARM Linux
2012-09-11 14:44         ` Lars-Peter Clausen
2012-09-11 14:50           ` Artem Bityutskiy
2012-09-12  1:32             ` Greg Ungerer
2012-09-12 20:43               ` Lars-Peter Clausen
2012-09-15 21:31                 ` Russell King - ARM Linux
2012-09-16  0:15                   ` Greg Ungerer
2012-09-18  8:00                   ` Thierry Reding
2012-09-18  9:35                     ` Russell King - ARM Linux
2012-09-18 11:25                       ` Thierry Reding [this message]
2012-09-18 20:40                         ` Russell King - ARM Linux
2012-09-19  6:55                           ` Thierry Reding
2012-09-11 17:51           ` Russell King - ARM Linux
2012-09-10  3:10 ` Greg Ungerer

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=20120918112555.GA21004@avionic-0098.mockup.avionic-design.de \
    --to=thierry.reding@avionic-design.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dedekind1@gmail.com \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=julia.lawall@lip6.fr \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mturquette@ti.com \
    --cc=stable@vger.kernel.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).