From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: maarten.lankhorst@linux.intel.com, daniel.vetter@ffwll.ch,
dh.herrmann@gmail.com, tvrtko.ursulin@intel.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/core: Do not preserve framebuffer on rmfb, v4." failed to apply to 4.6-stable tree
Date: Tue, 21 Jun 2016 22:13:45 -0700 [thread overview]
Message-ID: <20160622051345.GC20810@kroah.com> (raw)
In-Reply-To: <5762689B.6010404@vmware.com>
On Thu, Jun 16, 2016 at 10:51:39AM +0200, Thomas Hellstrom wrote:
> Hi!
>
> Anyone working on the backport?
> I guess there already is a backported version, right?
There is? Where?
next prev parent reply other threads:[~2016-06-22 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 20:48 FAILED: patch "[PATCH] drm/core: Do not preserve framebuffer on rmfb, v4." failed to apply to 4.6-stable tree gregkh
2016-06-16 8:51 ` Thomas Hellstrom
2016-06-22 5:13 ` Greg KH [this message]
2016-06-22 5:20 ` Maarten Lankhorst
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=20160622051345.GC20810@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dh.herrmann@gmail.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=thellstrom@vmware.com \
--cc=tvrtko.ursulin@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).