public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Greg Ungerer <gerg@snapgear.com>,
	dedekind1@gmail.com,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Mike Turquette <mturquette@ti.com>,
	Greg Ungerer <gerg@uclinux.org>,
	Julia Lawall <julia.lawall@lip6.fr>,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH] clk: Make the managed clk functions generically available
Date: Sat, 15 Sep 2012 22:31:52 +0100	[thread overview]
Message-ID: <20120915213151.GM12245@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <5050F3DB.1050202@metafoo.de>

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?

(Cc on this thread to stable added so they can hear the reply... so if
it does end up with a Cc: being added to the commit, they have the
background... this is *not* a stable submission request.)

  parent reply	other threads:[~2012-09-15 21:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1347202862-1617-1-git-send-email-lars@metafoo.de>
2012-09-09 20:57 ` [PATCH] clk: Make the managed clk functions generically available Russell King - ARM Linux
2012-09-09 23:50 ` Mark Brown
     [not found] ` <20120909235059.GA2643@sirena.org.uk>
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
     [not found]         ` <504F4E36.20309@metafoo.de>
2012-09-11 14:50           ` Artem Bityutskiy
2012-09-12  1:32             ` Greg Ungerer
2012-09-12 20:43               ` Lars-Peter Clausen
     [not found]               ` <5050F3DB.1050202@metafoo.de>
2012-09-15 21:31                 ` Russell King - ARM Linux [this message]
2012-09-16  0:15                   ` Greg Ungerer
2012-09-18  8:00                   ` Thierry Reding
2012-09-18  9:35                     ` Russell King - ARM Linux
     [not found]                     ` <20120918093536.GV12245@n2100.arm.linux.org.uk>
2012-09-18 11:25                       ` Thierry Reding
2012-09-18 20:40                         ` Russell King - ARM Linux
     [not found]                         ` <20120918204014.GY12245@n2100.arm.linux.org.uk>
2012-09-19  6:55                           ` Thierry Reding
2012-09-11 17:51           ` Russell King - ARM Linux
2012-09-10  3:10 ` Greg Ungerer
2012-09-09 15:01 Lars-Peter Clausen

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=20120915213151.GM12245@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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@lists.linux-m68k.org \
    --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