From: Zhi Wang <zhi.a.wang@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org,
"Michał Winiarski" <michal.winiarski@intel.com>,
"Michel Thierry" <michel.thierry@intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
"Zhenyu Wang" <zhenyuw@linux.intel.com>,
"Zhiyuan Lv" <zhiyuan.lv@intel.com>
Subject: Re: [PATCH 1/3] drm/i915: Move the release of PT page to the upper caller
Date: Sat, 01 Apr 2017 15:53:34 +0800 [thread overview]
Message-ID: <58DF5C7E.5030707@intel.com> (raw)
In-Reply-To: <20170401065140.GB14971@kroah.com>
Hi Greg:
Thanks for the explanation! :P I should CC you also in those
patches. My mistake! Wait a second! :P
On 04/01/17 14:51, Greg KH wrote:
> On Sat, Apr 01, 2017 at 02:08:27PM +0800, Zhi Wang wrote:
>> Hi Greg:
>> Is there anything else I should do to let patches that has already been
>> merged by linux-stable land in new 4.10.x tag? I have re-sent those patches
>> with the #v4.10+ tag, but looks they still haven't been merged.
> Ah, I totally missed these as it was not obvious at all that they were
> wanted to go into a stable tree, and were already upstream.
>
> You need to be a bit more specific, if you can include the "this is
> commit XXXXXX" at the top of the email, that would be great, as we need
> that information (and I don't see it in these patches at all, so it is
> why I missed them.)
>
> Can you fix that up and resend these?
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2017-04-01 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 1:57 [PATCH 1/3] drm/i915: Move the release of PT page to the upper caller Zhi Wang
2017-03-27 1:57 ` [PATCH 2/3] drm/i915: Let execlist_update_context() cover !FULL_PPGTT mode Zhi Wang
2017-03-27 1:57 ` [PATCH 3/3] drm/i915: A hotfix for making aliasing PPGTT work for GVT-g Zhi Wang
2017-04-01 6:08 ` [PATCH 1/3] drm/i915: Move the release of PT page to the upper caller Zhi Wang
2017-04-01 6:51 ` Greg KH
2017-04-01 7:53 ` Zhi Wang [this message]
2017-04-01 8:13 ` Greg KH
2017-04-05 6:33 Zhi Wang
2017-04-05 6:36 ` Zhi Wang
2017-04-05 8:01 ` Zhi Wang
2017-04-05 8:20 ` Greg KH
2017-04-05 8:14 ` Zhi Wang
2017-04-06 7:59 ` Greg KH
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=58DF5C7E.5030707@intel.com \
--to=zhi.a.wang@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=michal.winiarski@intel.com \
--cc=michel.thierry@intel.com \
--cc=stable@vger.kernel.org \
--cc=zhenyuw@linux.intel.com \
--cc=zhiyuan.lv@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.