From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/i915/dp: Fix dsc bpp calculations, v5.
Date: Wed, 25 Sep 2019 22:43:01 +0000 [thread overview]
Message-ID: <20190925224302.A6505208C3@mail.kernel.org> (raw)
In-Reply-To: <20190925082110.17439-1-maarten.lankhorst@linux.intel.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: d9218c8f6cf4 drm/i915/dp: Add helpers for Compressed BPP and Slice Count for DSC.
The bot has tested the following trees: v5.3.1, v5.2.17.
v5.3.1: Build OK!
v5.2.17: Failed to apply! Possible dependencies:
3c053a96ef5f ("drm/i915/dp: Program VSC Header and DB for Pixel Encoding/Colorimetry Format")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-25 22:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 8:21 [PATCH 1/2] drm/i915/dp: Fix dsc bpp calculations, v5 Maarten Lankhorst
2019-09-25 8:21 ` [PATCH 2/2] drm/i915: Add hardware readout for FEC Maarten Lankhorst
2019-09-25 9:10 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/dp: Fix dsc bpp calculations, v5 Patchwork
2019-09-25 9:56 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-25 10:26 ` [Intel-gfx] [PATCH 1/2] " Ville Syrjälä
2019-09-25 10:34 ` Maarten Lankhorst
2019-09-25 10:40 ` Ville Syrjälä
2019-09-25 22:43 ` Sasha Levin [this message]
2019-09-25 23:14 ` ✓ Fi.CI.IGT: success for series starting with [1/2] " 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=20190925224302.A6505208C3@mail.kernel.org \
--to=sashal@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox