All of lore.kernel.org
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/7] LPC32xx: clock.c: USB PLL fix
Date: Wed, 01 Feb 2012 14:27:11 +0100	[thread overview]
Message-ID: <4F293DAF.4050402@antcom.de> (raw)
In-Reply-To: <20120131103401.GJ2471@pengutronix.de>

Hi Wolfram,

Thanks for reviewing my patches! I collected (and applied) all your
suggestions and will re-post the series as a patch update for applying
to the mainline tree.

On 01/31/2012 11:34 AM, Wolfram Sang wrote:
> I remember we needed that fix back then as well, so I am tempted to
> ack it. However, I'd like to test it but USB is currently not
> available. Do you happen to have a USB fixing commit just to test
> (can be hackish)?

I'm posting this one separately (to be applied on top of all my and
your posted patches).

What do you think about mainline-integrating it?

Thanks in advance!

WARNING: multiple messages have this Message-ID (diff)
From: Roland Stigge <stigge@antcom.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: bangaragiri.g@nxp.com, srinivas.bakki@nxp.com,
	sundarapandian.andithevar@nxp.com, linus.walleij@linaro.org,
	linux-kernel@vger.kernel.org, kevin.wells@nxp.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 6/7] LPC32xx: clock.c: USB PLL fix
Date: Wed, 01 Feb 2012 14:27:11 +0100	[thread overview]
Message-ID: <4F293DAF.4050402@antcom.de> (raw)
In-Reply-To: <20120131103401.GJ2471@pengutronix.de>

Hi Wolfram,

Thanks for reviewing my patches! I collected (and applied) all your
suggestions and will re-post the series as a patch update for applying
to the mainline tree.

On 01/31/2012 11:34 AM, Wolfram Sang wrote:
> I remember we needed that fix back then as well, so I am tempted to
> ack it. However, I'd like to test it but USB is currently not
> available. Do you happen to have a USB fixing commit just to test
> (can be hackish)?

I'm posting this one separately (to be applied on top of all my and
your posted patches).

What do you think about mainline-integrating it?

Thanks in advance!

  reply	other threads:[~2012-02-01 13:27 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 16:02 [PATCH v2 1/7] LPC32xx: clock.c: Missing header file Roland Stigge
2012-01-30 16:02 ` Roland Stigge
2012-01-30 16:02 ` [PATCH v2 2/7] LPC32xx: clock.c: jiffies wrapping Roland Stigge
2012-01-30 16:02   ` Roland Stigge
2012-01-31 10:24   ` Wolfram Sang
2012-01-31 10:24     ` Wolfram Sang
2012-01-30 16:02 ` [PATCH v2 3/7] LPC32xx: clock.c: Clock registration fixes Roland Stigge
2012-01-30 16:02   ` Roland Stigge
2012-01-30 16:02 ` [PATCH v2 4/7] LPC32xx: clock.c: MMC update Roland Stigge
2012-01-30 16:02   ` Roland Stigge
2012-01-30 16:02 ` [PATCH v2 5/7] LPC32xx: clock.c: warning fix Roland Stigge
2012-01-30 16:02   ` Roland Stigge
2012-01-31 10:26   ` Wolfram Sang
2012-01-31 10:26     ` Wolfram Sang
2012-01-30 16:02 ` [PATCH v2 6/7] LPC32xx: clock.c: USB PLL fix Roland Stigge
2012-01-30 16:02   ` Roland Stigge
2012-01-31 10:34   ` Wolfram Sang
2012-01-31 10:34     ` Wolfram Sang
2012-02-01 13:27     ` Roland Stigge [this message]
2012-02-01 13:27       ` Roland Stigge
2012-02-02 16:49       ` Wolfram Sang
2012-02-02 16:49         ` Wolfram Sang
2012-02-02 19:20         ` Roland Stigge
2012-02-02 19:20           ` Roland Stigge
2012-02-02 23:01           ` Wolfram Sang
2012-02-02 23:01             ` Wolfram Sang
2012-01-30 16:02 ` [PATCH v2 7/7] LPC32xx: clock.c: Fix mutex lock issues Roland Stigge
2012-01-30 16:02   ` Roland Stigge
2012-01-31 10:27   ` Wolfram Sang
2012-01-31 10:27     ` Wolfram Sang
2012-01-30 17:56 ` [PATCH v2 1/7] LPC32xx: clock.c: Missing header file Sergei Shtylyov
2012-01-30 17:56   ` Sergei Shtylyov
2012-01-31 10:22   ` Wolfram Sang
2012-01-31 10:22     ` Wolfram Sang

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=4F293DAF.4050402@antcom.de \
    --to=stigge@antcom.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.