From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] NXP LPC32xx Platform Updates for v4.6 #1
Date: Wed, 24 Feb 2016 13:36:33 -0800 [thread overview]
Message-ID: <20160224213633.GF10126@localhost> (raw)
In-Reply-To: <56BBE6E6.4080802@mleia.com>
Hi!
On Thu, Feb 11, 2016 at 03:41:58AM +0200, Vladimir Zapolskiy wrote:
> Hi Arnd, Olof, Kevin,
>
> please consider to include NXP LPC32xx platfrom updates (#1) for v4.6.
>
> The main change is a switchover to a common clock framework driver
> for LPC32xx, this also allows to reuse a shared LPC32xx clockevent
> driver, and hence remove legacy clock and timer drivers from
> arch/arm/mach-lpc32xx.
>
> I'm adding an official LPC32xx maintainer Roland to Cc, however
> he seems to be unresponsive for a quite long time (since 2014).
>
> ----------------------------------------------------------------
>
> The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
>
> Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
>
> are available in the git repository at:
>
> https://github.com/vzapolskiy/linux.git lpc32xx/soc
>
> for you to fetch changes up to 0ac1a101f5dd28c3894be3c0230ee7ea2e05e8aa:
>
> arm: lpc32xx: remove direct control of GPIOs from shared mach file (2016-02-11 02:27:04 +0200)
In the future, please use the decription you wrote above as part of a tag
description, and sign your tags. For extra credit, get other kernel developers
to sign your key (easiest done at conferences, but maybe there are other
developers in your local area that you can meet up with).
It indeed seems like Roland has gone silent lately. This happens from time to
time, but it's always good to know if it's intentional (and if he's coming
back) or not. Meanwhile, we can merge patches after review but I don't have
hardware to test on so I'd have to rely on you getting that right. If we get
regression reports we'll have to re-evaluate the approach. :)
Roland, any chance we can get a word from you on this? Thanks!
-Olof
next prev parent reply other threads:[~2016-02-24 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 1:41 [GIT PULL] NXP LPC32xx Platform Updates for v4.6 #1 Vladimir Zapolskiy
2016-02-24 21:36 ` Olof Johansson [this message]
2016-02-25 14:14 ` Sylvain Lemieux
2016-02-29 0:18 ` Vladimir Zapolskiy
2016-02-29 13:35 ` Sylvain Lemieux
2016-03-02 22:56 ` Vladimir Zapolskiy
2016-03-02 23:27 ` Arnd Bergmann
2016-03-03 2:05 ` Vladimir Zapolskiy
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=20160224213633.GF10126@localhost \
--to=olof@lixom.net \
--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).