From: Gerd Hoffmann <kraxel@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Gabriel Krisman Bertazi <krisman@collabora.co.uk>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm: qxl: Drop misleading comment
Date: Tue, 31 Jan 2017 17:30:18 +0100 [thread overview]
Message-ID: <1485880218.1076.4.camel@redhat.com> (raw)
In-Reply-To: <20170127135305.ivlse3xpyho3qhb7@phenom.ffwll.local>
On Fr, 2017-01-27 at 14:53 +0100, Daniel Vetter wrote:
> On Fri, Jan 27, 2017 at 09:20:42AM +0100, Gerd Hoffmann wrote:
> > On Do, 2017-01-26 at 23:05 -0200, Gabriel Krisman Bertazi wrote:
> > > No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
> > > output"). qxl_num_crtc defaults to 4 and is configurable as a module
> > > parameter.
> >
> > Picked up patches 1-3 for drm-qemu branch.
> >
> > Patch 4 doesn't apply and seems to have a dependency on out-of-tree
> > changes, git am fails to do a 3way merge due to missing commits (trying
> > to apply to 4.10-rc5).
>
> It needs the demidlayer that's already in drm-next ...
Ok, added all four patches to drm-qemu.
drm-qemu is based on drm-misc-next now and basically just a staging
branch where I can test patches before pushing them to drm-misc-next.
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-01-31 16:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 1:05 [PATCH 1/4] drm: qxl: Drop misleading comment Gabriel Krisman Bertazi
2017-01-27 1:05 ` [PATCH 2/4] drm: qxl: Drop duplicated device pointer attribute Gabriel Krisman Bertazi
2017-01-27 1:23 ` Emil Velikov
2017-01-27 1:24 ` Emil Velikov
2017-01-27 1:05 ` [PATCH 3/4] drm: qxl: Drop duplicated pci_device " Gabriel Krisman Bertazi
2017-01-27 1:05 ` [PATCH 4/4] drm: qxl: Embed drm_device into driver structure Gabriel Krisman Bertazi
2017-01-27 7:35 ` [PATCH 1/4] drm: qxl: Drop misleading comment Daniel Vetter
2017-01-27 7:37 ` Daniel Vetter
2017-01-27 8:20 ` Gerd Hoffmann
2017-01-27 13:53 ` Daniel Vetter
2017-01-27 16:41 ` Gabriel Krisman Bertazi
2017-01-30 8:17 ` Gerd Hoffmann
2017-01-30 8:27 ` Daniel Vetter
2017-01-30 9:41 ` Gerd Hoffmann
2017-01-30 9:52 ` Daniel Vetter
2017-01-30 17:14 ` Gerd Hoffmann
2017-01-31 7:58 ` Daniel Vetter
2017-01-31 8:55 ` Gerd Hoffmann
2017-01-31 9:04 ` Daniel Vetter
2017-01-31 9:46 ` Jani Nikula
2017-01-31 10:19 ` Gerd Hoffmann
2017-01-31 11:28 ` Jani Nikula
2017-01-31 16:41 ` Gerd Hoffmann
2017-01-31 16:30 ` Gerd Hoffmann [this message]
2017-01-31 17:07 ` Gabriel Krisman Bertazi
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=1485880218.1076.4.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=krisman@collabora.co.uk \
/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