public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC
Date: Wed, 27 Apr 2016 11:39:58 +0200	[thread overview]
Message-ID: <4622738.ujCxg0gb7N@wuerfel> (raw)
In-Reply-To: <1461714919-25577-1-git-send-email-vz@mleia.com>

On Wednesday 27 April 2016 02:55:16 Vladimir Zapolskiy wrote:
> 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:
> 

Looks good. Let's give Roland some time to reply (hopefully with
and Ack), and then merge it for 4.7.

Thanks,

	Arnd

  parent reply	other threads:[~2016-04-27  9:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 23:55 [PATCH 0/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC Vladimir Zapolskiy
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 ` Arnd Bergmann [this message]
2016-04-28 23:10   ` [PATCH 0/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC 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=4622738.ujCxg0gb7N@wuerfel \
    --to=arnd@arndb.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