All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, radhakrishna.sripada@intel.com,
	rodrigo.vivi@intel.com, fred.gao@intel.com,
	zhenyuw@linux.intel.com, chuanxiao.dong@intel.com,
	zhi.a.wang@intel.com
Subject: drm/i915 fixes that failed to backport to v4.15
Date: Tue, 21 Nov 2017 12:20:00 +0200	[thread overview]
Message-ID: <87lgj0ue5r.fsf@intel.com> (raw)


All, the following fixes selected based on the Fixes: tag failed to
backport to drm-next heading to v4.15.

8cf80a2e4b31 ("drm/i915/gvt: Rename reserved ring buffer")

This one I think shouldn't have included a Fixes: line in the first
place. While technically a rename can be a fix, I consider Fixes: to
indicate things that have a functional significance to the end user.

f2880e04f3a5 ("drm/i915/gvt: Move request alloc to dispatch_workload path only")
0cfecb7c4b9b ("Revert "drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk"")

If these are needed in v4.15, please provide backports based on the
drm-intel-next-fixes branch.

BR,
Jani.

-- 
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:[~2017-11-21 10:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 10:20 Jani Nikula [this message]
2017-11-22  6:10 ` drm/i915 fixes that failed to backport to v4.15 Zhenyu Wang
2017-12-06 22:25 ` [PATCH] Revert "drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk" Rodrigo Vivi
2017-12-07 14:58   ` Joonas Lahtinen
2017-12-06 22:28 ` ✗ Fi.CI.BAT: failure for Revert "drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk" (rev2) Patchwork

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=87lgj0ue5r.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chuanxiao.dong@intel.com \
    --cc=fred.gao@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=radhakrishna.sripada@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhi.a.wang@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.