From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Zack Rusin <zackr@vmware.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm/vmwgfx fixes for 5.12-rc8
Date: Wed, 21 Apr 2021 21:02:26 +0200 [thread overview]
Message-ID: <CAKMK7uExn01wSKtAgr6P0npEhdeDe1+ie1yH5Pz0tFx7QWjeFw@mail.gmail.com> (raw)
In-Reply-To: <2dea2bb1-ff91-601d-5945-f9974d3f050b@vmware.com>
On Wed, Apr 21, 2021 at 7:00 PM Zack Rusin <zackr@vmware.com> wrote:
>
> On 4/17/21 7:02 PM, Dave Airlie wrote:
> > Hi Zack,
> >
> > Please make sure to always cc dri-devel and/or Daniel on these so if
> > I'm away they don't get lost, but also so that they make it into
> > patchwork for processing.
> >
> > If you have a chance can you resend it, I'll see if we can process
> > this out of band and get it to Linus before release.
> Hi, Dave.
>
> Thank you! I just noticed that you've sent it out. Would you still like me to resend it through dri-devel? The patches all went through dri-devel already, I just assumed that from dri-misc docs that drm-misc-fixes wouldn't be merged again until after 5.13 was out which is why I went directly.
drm-misc-fixes will get pulled into the merge window when it misses
the last release (which would be 5.12). drm-misc-next-fixes is the
special branch which is for fixes during the merge window time, for
issues in drm-next (so for 5.13).
I know that ideally maintainters would just cherry-pick bugfixes to
the right release branch (like on mesa or xserver or well any other
reasonable project), but since drm-misc is volunteer run committers
need to pick the right branch. But aside from that drm-misc is always
open for bugfixes (and also always open for feature work).
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-21 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f7add0a2-162e-3bd2-b1be-344a94f2acbf@vmware.com>
2021-04-17 23:02 ` [git pull] drm/vmwgfx fixes for 5.12-rc8 Dave Airlie
2021-04-19 18:48 ` Daniel Vetter
2021-04-21 17:00 ` Zack Rusin
2021-04-21 19:02 ` Daniel Vetter [this message]
2021-04-17 23:48 Dave Airlie
2021-04-17 23:48 ` Dave Airlie
2021-04-18 3:29 ` pr-tracker-bot
2021-04-18 3:29 ` pr-tracker-bot
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=CAKMK7uExn01wSKtAgr6P0npEhdeDe1+ie1yH5Pz0tFx7QWjeFw@mail.gmail.com \
--to=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=zackr@vmware.com \
/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.