From: alexandre.belloni@bootlin.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: at91: SoC for 4.17
Date: Sat, 10 Mar 2018 06:20:07 +0100 [thread overview]
Message-ID: <20180310052007.GA5536@piout.net> (raw)
Arnd, Olof,
It has been two years that Atmel merge with Microchip, rename where
relevant.
This is based on my fixes PR which is already in next/soc. Tell me if
this is not right.
The following changes since commit c8d5dcf122b194e897d2a6311903eae0c1023325:
MAINTAINERS: ARM: at91: update my email address (2018-02-22 16:22:15 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git tags/at91-ab-4.17-soc
for you to fetch changes up to ed08b63c8b3e23dfc8a32f0b450a23a35a3d91b4:
ARM: at91: Kconfig: Update company to Microchip (2018-02-28 16:21:51 +0100)
----------------------------------------------------------------
AT91 SoC for 4.17:
- Rename Atmel to Microhip in MAINTAINERS, Documentation and Kconfig
----------------------------------------------------------------
Nicolas Ferre (3):
MAINTAINERS: ARM: at91: update entry for ARM/Microchip
Documentation: at91: Update Microchip SoC documentation
ARM: at91: Kconfig: Update company to Microchip
Documentation/arm/{Atmel => Microchip}/README | 52 +++++++++++++--------------
MAINTAINERS | 42 +++++++++++-----------
arch/arm/mach-at91/Kconfig | 14 ++++----
3 files changed, 53 insertions(+), 55 deletions(-)
rename Documentation/arm/{Atmel => Microchip}/README (64%)
--
Alexandre Belloni, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2018-03-10 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 5:20 Alexandre Belloni [this message]
2018-03-12 14:26 ` [GIT PULL] ARM: at91: SoC for 4.17 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=20180310052007.GA5536@piout.net \
--to=alexandre.belloni@bootlin.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).