From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: add RV1108 Rockchip soc to maintained files
Date: Sun, 18 Jun 2017 18:54:29 -0700 [thread overview]
Message-ID: <20170619015429.GA30022@localhost> (raw)
In-Reply-To: <20170607110627.4678-1-heiko@sntech.de>
On Wed, Jun 07, 2017 at 01:06:27PM +0200, Heiko Stuebner wrote:
> The RV1108, as a soc targetted at visual applications, does not follow
> the usual RKxxxx naming scheme and thus falls through the cracks of
> the current file list for Rockchip socs in MAINTAINERS.
>
> The driver side does not pose a problem, as the rv1108 shares most
> functionality with other Rockchip socs as usual, so we only need to
> add an expression catching the rv1108* arm32 devicetree files.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> This could either be applied by arm-soc people directly, or I can
> integrate it into my arm32-dts-branch.
Applied to next/fixes-non-critical
-Olof
prev parent reply other threads:[~2017-06-19 1:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 11:06 [PATCH] MAINTAINERS: add RV1108 Rockchip soc to maintained files Heiko Stuebner
2017-06-19 1:54 ` Olof Johansson [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=20170619015429.GA30022@localhost \
--to=olof@lixom.net \
--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).