From: Daniel Vetter <daniel@ffwll.ch>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v3 3/3] MAINTAINERS: Add ASPEED BMC GFX DRM driver entry
Date: Wed, 3 Apr 2019 09:11:16 +0200 [thread overview]
Message-ID: <20190403071115.GO2665@phenom.ffwll.local> (raw)
In-Reply-To: <20190403001909.31637-4-joel@jms.id.au>
On Wed, Apr 03, 2019 at 10:49:09AM +1030, Joel Stanley wrote:
> This hardware is found inside ASPEED Baseboard Management Controller
> (BMC) system on chips. It is called the 'SOC Display Controller' or 'GFX'.
>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
> MAINTAINERS | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c18f5f10cf91..c3ad730e26f3 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4909,6 +4909,14 @@ M: Dave Airlie <airlied@redhat.com>
> S: Odd Fixes
> F: drivers/gpu/drm/ast/
>
> +DRM DRIVER FOR ASPEED BMC GFX
> +M: Joel Stanley <joel@jms.id.au>
> +L: linux-aspeed at lists.ozlabs.org
> +T: git git://anongit.freedesktop.org/drm/drm-misc
Do you have the fdo account request for drm-misc already?
-Daniel
> +S: Supported
> +F: drivers/gpu/drm/aspeed/
> +F: Documentation/devicetree/bindings/gpu/aspeed-gfx.txt
> +
> DRM DRIVER FOR BOCHS VIRTUAL GPU
> M: Gerd Hoffmann <kraxel@redhat.com>
> L: virtualization at lists.linux-foundation.org
> --
> 2.20.1
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2019-04-03 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 0:19 [PATCH v3 0/3] drm: Add ASPEED BMC 'GFX' driver Joel Stanley
2019-04-03 0:19 ` [PATCH v3 1/3] dt-bindings: gpu: Add ASPEED GFX bindings document Joel Stanley
2019-04-06 6:06 ` Rob Herring
2019-04-03 0:19 ` [PATCH v3 2/3] drm: Add ASPEED GFX driver Joel Stanley
2019-04-03 0:19 ` [PATCH v3 3/3] MAINTAINERS: Add ASPEED BMC GFX DRM driver entry Joel Stanley
2019-04-03 7:11 ` Daniel Vetter [this message]
2019-04-03 7:30 ` Joel Stanley
2019-04-03 7:36 ` Joel Stanley
2019-04-04 1:04 ` Andrew Jeffery
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=20190403071115.GO2665@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=linux-aspeed@lists.ozlabs.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