All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: drm-intel geared towards v4.18
Date: Wed, 14 Mar 2018 13:46:48 +0200	[thread overview]
Message-ID: <87po46nal3.fsf@intel.com> (raw)


All, as Joonas sent the final drm-intel feature pull request for v4.17
[1], the drm-intel-next-queued branch is now geared towards v4.18.

As Joonas follows through with fixes for v4.17, I take over features for
v4.18. Rodrigo continues with the final v4.16 development cycles.

The merge deadline for features aiming for v4.18 is in the v4.17-rc5
timeframe. Based on the crystal ball [2], I predict this to be around
May 27th. You have about 2½ months to get your patches in.

Happy hacking,
Jani.


[1] http://mid.mail-archive.com/152086716471.10203.338554124094146849@jlahtine-desk.ger.corp.intel.com
[2] http://phb-crystal-ball.org/


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

                 reply	other threads:[~2018-03-14 11:46 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=87po46nal3.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@freedesktop.org \
    --cc=rodrigo.vivi@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 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.