From: Gerd Hoffmann <kraxel@redhat.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Update git entries for drivers in drm-misc
Date: Tue, 28 Feb 2017 20:51:01 +0100 [thread overview]
Message-ID: <1488311461.26614.55.camel@redhat.com> (raw)
In-Reply-To: <20170228193657.3559-1-daniel.vetter@ffwll.ch>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6cd8945b9094..e55a648e77ec 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4174,7 +4174,7 @@ F: drivers/gpu/drm/bridge/
> DRM DRIVER FOR BOCHS VIRTUAL GPU
> M: Gerd Hoffmann <kraxel@redhat.com>
> L: virtualization@lists.linux-foundation.org
> -T: git git://git.kraxel.org/linux drm-qemu
> +T: git git://anongit.freedesktop.org/drm/drm-misc
I' still using the drm-qemu branch as staging area, but yes, it probably
makes sense to just list drm-misc as this is the tree where the changes
are actually merged from and typically patches don't sit in drm-qemu
very long ...
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
cheers,
Gerd
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-02-28 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 19:36 [PATCH] MAINTAINERS: Update git entries for drivers in drm-misc Daniel Vetter
2017-02-28 19:51 ` Gerd Hoffmann [this message]
2017-02-28 20:11 ` Eric Anholt
2017-02-28 20:19 ` Boris Brezillon
2017-03-01 7:24 ` Daniel Vetter
2017-03-01 13:23 ` Shawn Guo
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=1488311461.26614.55.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=shawnguo@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.