public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: Zynq clk fixes
Date: Fri, 26 Jul 2013 15:25:01 -0700	[thread overview]
Message-ID: <20130726222501.7598.33060@quantum> (raw)
In-Reply-To: <a76b3a5d-dadc-43b3-87ee-3c65258c15d7@CO1EHSMHS029.ehs.local>

Quoting S?ren Brinkmann (2013-07-26 14:11:52)
> On Fri, Jul 26, 2013 at 01:07:03PM -0700, Mike Turquette wrote:
> > Quoting Michal Simek (2013-07-26 05:09:58)
> > > Hi Mike, [cc: Arnd and Olof]
> > > 
> > > Soren has found two bug fixes in zynq clk code.
> > > Can you please add these two patches to your tree?
> > > Will be great if you can add them to v3.11.
> > > 
> > > Arnd, Olof: I expect that all these clock changes should go through Mike.
> > > If I am wrong please let me know.
> > 
> > Looks right to me. Do these fix regressions in the current -rc cycle?
> 
> I doubt there are real regressions. But since it's still early in
> the release cycle and the driver was added in this merge window, I'd prefer
> having it hit a release kernel with these fixes included.

I've taken these into clk-fixes and added the following to the changelog
for each patch:

"This does not fix a specific regression but the clock driver was merged
for 3.11-rc1, so best to fix the known bugs before the release."

Regards,
Mike

> 
>         S?ren

  reply	other threads:[~2013-07-26 22:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 12:09 Zynq clk fixes Michal Simek
2013-07-26 20:07 ` Mike Turquette
2013-07-26 21:11   ` Sören Brinkmann
2013-07-26 22:25     ` Mike Turquette [this message]
2013-07-26 22:26       ` Sören Brinkmann
2013-08-13 14:30       ` Michal Simek
2013-08-15 17:58         ` Mike Turquette

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=20130726222501.7598.33060@quantum \
    --to=mturquette@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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