From: Vladimir Zapolskiy <vz@mleia.com>
To: Sylvain Lemieux <slemieux.tyco@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@kernel.org>
Cc: Roland Stigge <stigge@antcom.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC
Date: Wed, 27 Apr 2016 02:55:16 +0300 [thread overview]
Message-ID: <1461714919-25577-1-git-send-email-vz@mleia.com> (raw)
Roland Stigge added initial support of NXP LPC32xx SoC series and
first boards powered by it, but for a while since v3.18-rc1 the
SoC support is unmaintained and became stale.
Vladimir Zapolskiy and Sylvain Lemieux expressed interest in
continuation of NXP LPC32xx maintenance, reflect this in MAINTAINERS
record file for better communication with Linux kernel community.
The maintenance change is in agreement with Arnd Bergmann:
http://www.spinics.net/lists/arm-kernel/msg498129.html
Vladimir Zapolskiy (3):
MAINTAINERS: move ARM/NXP LPC32xx record to ARM section
MAINTAINERS: add new maintainers of NXP LPC32xx SoC
MAINTAINERS: add ARM/NXP LPC32XX SoC specific drivers to the section
MAINTAINERS | 20 ++++++++++++++------
1 file changed, 14 insertions(+), 6 deletions(-)
--
2.8.0.rc3
next reply other threads:[~2016-04-26 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 23:55 Vladimir Zapolskiy [this message]
2016-04-26 23:55 ` [PATCH 1/3] MAINTAINERS: move ARM/NXP LPC32xx record to ARM section Vladimir Zapolskiy
2016-04-26 23:55 ` [PATCH 2/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC Vladimir Zapolskiy
2016-04-26 23:55 ` [PATCH 3/3] MAINTAINERS: add ARM/NXP LPC32XX SoC specific drivers to the section Vladimir Zapolskiy
2016-04-27 9:39 ` [PATCH 0/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC Arnd Bergmann
2016-04-28 23:10 ` Vladimir Zapolskiy
2016-04-28 23:14 ` Arnd Bergmann
2016-04-29 0:02 ` Vladimir Zapolskiy
2016-05-09 13:37 ` 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=1461714919-25577-1-git-send-email-vz@mleia.com \
--to=vz@mleia.com \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=slemieux.tyco@gmail.com \
--cc=stigge@antcom.de \
/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
all inboxes | Powered by JetHome®