From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX maintainers update for 4.18
Date: Mon, 28 May 2018 16:15:50 +0800 [thread overview]
Message-ID: <20180528081549.GD3143@dragon> (raw)
Hi Arnd, Olof,
I'm not sure which one is easier for you. You can pull the request or
apply the patch to some arm-soc branch directly.
Shawn
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-maintainers-4.18
for you to fetch changes up to c309f0cdc30667efd233f1220587fb0b18c8423b:
MAINTAINERS: add NXP linux team maillist as i.MX reviewer (2018-05-28 15:55:07 +0800)
----------------------------------------------------------------
i.MX maintainers update for 4.18:
- Add NXP linux team as a reviewer for i.MX platform support.
----------------------------------------------------------------
Dong Aisheng (1):
MAINTAINERS: add NXP linux team maillist as i.MX reviewer
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
next reply other threads:[~2018-05-28 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 8:15 Shawn Guo [this message]
2018-06-02 8:16 ` [GIT PULL] i.MX maintainers update for 4.18 Olof Johansson
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=20180528081549.GD3143@dragon \
--to=shawnguo@kernel.org \
--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).