linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Fix LPC32XX's clock.c
Date: Sat, 28 Jan 2012 11:41:50 +0100	[thread overview]
Message-ID: <4F23D0EE.8000103@antcom.de> (raw)
In-Reply-To: <20120127223211.GA27425@pengutronix.de>

On 27/01/12 23:32, Wolfram Sang wrote:
>> [clock.c]
> This needs to be split up further to make reviewing easier, I'd
> say. From a glimpse, I'd guess:
> 
> - locking changes - usb fixes - adding MLC NAND - adding ADC

OK, will separate things out. Can move over the changes for ADC and
MLC NAND to the respected driver integration patches (following).

> I dunno, maybe the NXP git has the incremental changes? You should
> really CC Kevin Wells on your patches. Maybe he will wake up again,
> at least with some additional informaition.

Yes, I'm also re-forwarding all my integration patches to Kevin Wells
and his colleagues at NXP who also committed to git.lpclinux.com in
the past.

The patches have different sources, all collected together now:

* http://git.lpclinux.com/ (Kevin Wells et. al., NXP), repositories:
  - linux-2.6.27.8-lpc32xx.git
  - linux-2.6.34-lpc32xx.git
  - linux-2.6.39.2-lpc.git
* http://git.antcom.de/ (my repos)
  - linux-2.6, branch work92105

I basically collected the most recent versions and fixes from the
other different sources together and forward-ported to latest Linux
mainline. (Currently works really well for the WORK Microwave devices
based on LPC3250.) You can find many incremental changes in the above
repositories hopefully clearing things up.

Thanks in advance,

Roland

  reply	other threads:[~2012-01-28 10:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 14:17 [PATCH] Fix LPC32XX's clock.c Roland Stigge
2012-01-27 22:32 ` Wolfram Sang
2012-01-28 10:41   ` Roland Stigge [this message]
2012-01-28 16:00 ` Russell King - ARM Linux

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=4F23D0EE.8000103@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 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).