From: vz@mleia.com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: NXP LPC32xx Mach Updates for v4.7
Date: Fri, 29 Apr 2016 01:47:00 +0300 [thread overview]
Message-ID: <572292E4.9010209@mleia.com> (raw)
Hi Arnd, Olof, Kevin,
please consider to include NXP LPC32xx mach clean-up updates for v4.7.
I'm adding an official LPC32xx maintainer Roland to Cc, however
he seems to be unresponsive for a quite long time.
Thank you in advance.
The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
are available in the git repository at:
git://github.com/vzapolskiy/linux-lpc32xx.git tags/lpc32xx-soc-4.7
for you to fetch changes up to 71d42e9c71d7fca2eca98eac315cb485b5d2314d:
ARM: lpc32xx: remove duplicate const on lpc32xx_auxdata_lookup (2016-04-28 00:45:12 +0300)
----------------------------------------------------------------
NXP LPC32xx mach updates for v4.7
This includes a few nonfunctional clean-ups for NXP LPC32xx:
* removed leftover from restart code migration to a watchdog driver
* removed dead code leftovers from migration to CCF driver
* fix double const qualifier
----------------------------------------------------------------
Sylvain Lemieux (1):
ARM: lpc32xx: remove reboot header file
Vladimir Zapolskiy (2):
ARM: lpc32xx: remove leftovers of legacy clock source and provider drivers
ARM: lpc32xx: remove duplicate const on lpc32xx_auxdata_lookup
arch/arm/mach-lpc32xx/common.c | 95 -----------------------------------------
arch/arm/mach-lpc32xx/common.h | 24 +----------
arch/arm/mach-lpc32xx/phy3250.c | 2 +-
3 files changed, 2 insertions(+), 119 deletions(-)
next reply other threads:[~2016-04-28 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 22:47 Vladimir Zapolskiy [this message]
2016-05-09 13:56 ` NXP LPC32xx Mach Updates for v4.7 Arnd Bergmann
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=572292E4.9010209@mleia.com \
--to=vz@mleia.com \
--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).