From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, ARM Maintainers <arm@kernel.org>
Subject: Re: [PATCH 1/3] MAINTAINERS: ARM: at91: update entry for ARM/Microchip
Date: Wed, 28 Feb 2018 16:43:18 +0100 [thread overview]
Message-ID: <20180228154318.GN1479@piout.net> (raw)
In-Reply-To: <c00e7bf21945e844c6154b374924b7ff520d1316.1519829594.git.nicolas.ferre@microchip.com>
On 28/02/2018 at 15:56:41 +0100, Nicolas Ferre wrote:
> Change the entry name and move it to its alphabetical location.
> We move to ARM/Microchip instead of ARM/ATMEL to reflect the merger
> that is now nearly 2 years old.
> AT91 is kept as the identity of our community. The atmel pattern is
> obviously kept as well. I removed the names of the different SoCs as
> they are better exposed in the arch/arm/mach-at91/Kconfig entries.
>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> Hi,
>
> This patch goes on top of linux-next because Alexandre's email change is taken
> into account (already in arm-soc).
>
All applied in my at91-soc branch which takes care of the dependency
--
Alexandre Belloni, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-02-28 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 14:56 [PATCH 1/3] MAINTAINERS: ARM: at91: update entry for ARM/Microchip Nicolas Ferre
2018-02-28 14:56 ` [PATCH 2/3] Documentation: at91: Update Microchip SoC documentation Nicolas Ferre
2018-02-28 14:56 ` [PATCH 3/3] ARM: at91: Kconfig: Update company to Microchip Nicolas Ferre
2018-02-28 15:43 ` Alexandre Belloni [this message]
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=20180228154318.GN1479@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
/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