From: Greg KH <gregkh@linuxfoundation.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: stable@vger.kernel.org,
Anusha Srivatsa <anusha.srivatsa@intel.com>,
Manasi Navare <manasi.d.navare@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 5.0-stable] drm/i915: Do not enable FEC without DSC
Date: Thu, 2 May 2019 13:47:51 +0200 [thread overview]
Message-ID: <20190502114751.GB24696@kroah.com> (raw)
In-Reply-To: <20190430175054.21797-1-ville.syrjala@linux.intel.com>
On Tue, Apr 30, 2019 at 08:50:54PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> commit 5aae7832d1b4ec614996ea0f4fafc4d9855ec0b0 upstream.
Thanks for the backport, now queued up.
greg k-h
prev parent reply other threads:[~2019-05-02 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 9:25 FAILED: patch "[PATCH] drm/i915: Do not enable FEC without DSC" failed to apply to 5.0-stable tree gregkh
2019-04-30 17:50 ` [PATCH 5.0-stable] drm/i915: Do not enable FEC without DSC Ville Syrjala
2019-05-02 11:47 ` Greg KH [this message]
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=20190502114751.GB24696@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anusha.srivatsa@intel.com \
--cc=manasi.d.navare@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).