From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
<arm@kernel.org>,
soc@kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: [GIT PULL] ARM: mvebu: arm for v5.10 (#1)
Date: Thu, 24 Sep 2020 13:58:20 +0200 [thread overview]
Message-ID: <87mu1fgzdv.fsf@BL-laptop> (raw)
Hi,
Here is the first pull request for arm for mvebu for v5.10.
Gregory
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/gclement/mvebu tags/mvebu-arm-5.10-1
for you to fetch changes up to 399412cddd8cba0b9e8505d67d70103bb3b89c47:
MAINTAINERS: switch mvebu tree to kernel.org (2020-09-24 10:21:50 +0200)
----------------------------------------------------------------
mvebu arm for 5.10 (part 1)
Update MAINTAINER file:
- add new 98DX3236 based boards
- point new git repository for mvebu
----------------------------------------------------------------
Gregory CLEMENT (1):
MAINTAINERS: switch mvebu tree to kernel.org
Luka Kovacic (1):
MAINTAINERS: Add an entry for MikroTik CRS3xx 98DX3236 boards
MAINTAINERS | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-09-24 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 11:58 Gregory CLEMENT [this message]
2020-10-03 19:41 ` [GIT PULL] ARM: mvebu: arm for v5.10 (#1) Olof Johansson
2020-10-05 12:59 ` Gregory CLEMENT
-- strict thread matches above, loose matches on Subject: below --
2020-09-24 12:01 Gregory CLEMENT
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=87mu1fgzdv.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=soc@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.