From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>
Subject: drm-intel geared towards 4.19
Date: Mon, 11 Jun 2018 10:00:10 -0700 [thread overview]
Message-ID: <20180611170010.GL2228@intel.com> (raw)
Hi all,
As you might have noticed:
- 4.17 was released on 2018-06-03 [1]
- Jani has already started pull requests for 4.18 fixes and stabilization [2]
- I had just sent out the first pull of our stuff targeting 4.19. [3]
Based on the crystal-ball [4], I predict that our deadline for
pushing stuff to dinq that targets 4.19 will be around
July 18th.
After that Joonas will move dinq and drm-intel-next branches towards 4.20.
If you have any doubts or concerns please let me know.
Happy hacking,
Rodrigo.
[1] - https://lwn.net/Articles/756401/
[2] - https://lists.freedesktop.org/archives/intel-gfx/2018-June/167589.html
[3] - https://lists.freedesktop.org/archives/intel-gfx/2018-June/167800.html
[4] - http://phb-crystal-ball.org/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2018-06-11 17:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180611170010.GL2228@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).