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: Mon, 30 Jan 2017 18:14:49 +0100 [thread overview]
Message-ID: <1485796489.20455.66.camel@redhat.com> (raw)
In-Reply-To: <20170130095237.4ktkumbo4ngsidte@phenom.ffwll.local>
Hi,
> drm-misc runs with the committer model, i.e. a few maintainers to do pull
> requests and backmerges, a big pile of people directly pushing patches.
[ looked at docs too meanwhile ]
Sounds good. I guess switching over simplifies things for all of us.
We'll avoid issues like the one at hand. Patch flow would be faster
too. Right now I'm only doing 1-2 drm-qemu pull requests per kernel
release due to low patch volume even for all four qemu drivers combined.
> Someone wreaked the entire 01.org domain, but you can get at all the
> tooling and documentation with
>
> git://anongit.freedesktop.org/drm-intel maintainer-tools
Hmm. On a quick glance most of dim (except apply-patch) seems to be
more useful for maintainers which do merges etc, not so much for
committers.
I'm used to use https://github.com/stefanha/patches for qemu, and
started using it for drm-qemu too. It makes applying patches easier.
It manages a patch database, using notmuch mail storage, and can apply
patches and patch series from the patch database. That way I don't have
to save the patches as mbox somewhere. The tool also picks up
[Reviewed,Tested,Acked}-by lines from replies, and it stores the message
id (but unlike dim it doesn't build a patchwork link out of it).
See bfac9f4fb4d87881375ccdc5c85d5ad59f2f115d for example.
Would that format be acceptable for drm-misc?
> And then run make in there. We're not yet clear how exactly drivers within
> drm-misc would look like (wrt which drivers and how much review and stuff
> like that), hence the RFC.
Ok. How quickly could I start using drm-misc? I have some pending
patches for the 4.11 merge window. Any chance I can push them through
drm-misc-next? Or should I better send a pull req to Dave?
cheers,
Gerd
PS: I'm kraxel@freedesktop.org
_______________________________________________
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-30 17:14 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 [this message]
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
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=1485796489.20455.66.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