All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	dim-tools@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, Dave Airlie <airlied@redhat.com>
Subject: [Intel-gfx] [ANNOUNCE] upcoming mandated dim upgrade due to drm-intel branch change
Date: Mon, 30 Nov 2020 17:33:05 +0200	[thread overview]
Message-ID: <87sg8qkgge.fsf@intel.com> (raw)


TL;DR:
- On 2020-12-05, drm-intel-next-queued will be decommissioned
- drm-intel committers need to start using drm-intel-next instead
- Everyone needs to upgrade dim *after* the change


Full story:

For historical reasons, we've had separate drm-intel-next-queued
("dinq") and drm-intel-next ("din") branches for development and pull
requests, respectively. This split has not been necessary for a while
now, so we'll finally remove dinq, and start applying patches directly
to drm-intel-next.

We'll make the switch on 2020-12-05.

This change requires a flag-day change in dim, i.e. everyone will need
to upgrade dim *after* the switch. (The details of the flag-day change
are covered in [1].)

All the current dinq related commands and aliases (such as 'dim conq',
'dim aq', and 'dim pq') will continue to work, except they'll operate on
drm-intel-next.


BR,
Jani.


[1] http://marc.info/?i=20201113095658.16655-1-jani.nikula@intel.com


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

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	dim-tools@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Dave Airlie <airlied@redhat.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [ANNOUNCE] upcoming mandated dim upgrade due to drm-intel branch change
Date: Mon, 30 Nov 2020 17:33:05 +0200	[thread overview]
Message-ID: <87sg8qkgge.fsf@intel.com> (raw)


TL;DR:
- On 2020-12-05, drm-intel-next-queued will be decommissioned
- drm-intel committers need to start using drm-intel-next instead
- Everyone needs to upgrade dim *after* the change


Full story:

For historical reasons, we've had separate drm-intel-next-queued
("dinq") and drm-intel-next ("din") branches for development and pull
requests, respectively. This split has not been necessary for a while
now, so we'll finally remove dinq, and start applying patches directly
to drm-intel-next.

We'll make the switch on 2020-12-05.

This change requires a flag-day change in dim, i.e. everyone will need
to upgrade dim *after* the switch. (The details of the flag-day change
are covered in [1].)

All the current dinq related commands and aliases (such as 'dim conq',
'dim aq', and 'dim pq') will continue to work, except they'll operate on
drm-intel-next.


BR,
Jani.


[1] http://marc.info/?i=20201113095658.16655-1-jani.nikula@intel.com


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2020-11-30 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 15:33 Jani Nikula [this message]
2020-11-30 15:33 ` [ANNOUNCE] upcoming mandated dim upgrade due to drm-intel branch change Jani Nikula
2020-12-06  9:22 ` [Intel-gfx] " Jani Nikula
2020-12-06  9:22   ` Jani Nikula

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=87sg8qkgge.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.