From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Radhakrishna Sripada <radhakrishna.sripada@intel.com>
Subject: Re: Fixes that failed to cleanly apply to v4.15-rc1
Date: Tue, 05 Dec 2017 17:02:34 +0200 [thread overview]
Message-ID: <1512486154.9226.3.camel@linux.intel.com> (raw)
In-Reply-To: <1511859267.4761.15.camel@linux.intel.com>
Dropping GVT folks that are not affected.
Keeping Zhenyu and Zhi as a heads-up, there's no need for GVT pull for this rc?
On Tue, 2017-11-28 at 10:54 +0200, Joonas Lahtinen wrote:
> Hello,
>
> TL;DR Reply with backported patches for v4.15-rc1 latest TODAY
>
> Dear patch authors/Cc:s, the following patches failed to cleanly
> backport to v4.15-rc1, if you believe they still are valid patches to
> be included in drm-intel-fixes, please backport them and send them as a
> REPLY TO THIS EMAIL before the END OF TODAY.
<SNIP>
> 0cfecb7c4b9b ("Revert "drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk"")
This patch still fails to apply and I'm looking at -rc3 already.
Rodrigo and Radhakrishna, do we actually want to see the patch
backported?
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-12-05 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 8:54 Fixes that failed to cleanly apply to v4.15-rc1 Joonas Lahtinen
2017-11-28 9:27 ` Zhenyu Wang
2017-12-05 15:02 ` Joonas Lahtinen [this message]
2017-12-06 3:24 ` Zhenyu Wang
2018-01-02 11:53 ` Jani Nikula
2018-01-02 20:18 ` [PATCH] drm/i915: Apply Display WA #1183 on skl, kbl, and cfl Lucas De Marchi
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=1512486154.9226.3.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=radhakrishna.sripada@intel.com \
--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.