From: Greg KH <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Eric Blau" <eblau@eblau.com>,
stable@vger.kernel.org, "Chris Wilson" <chris@chris-wilson.co.uk>,
"Michel Thierry" <michel.thierry@intel.com>,
"Mika Kuoppala" <mika.kuoppala@intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Michał Winiarski" <michal.winiarski@intel.com>,
"Daniel Vetter" <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Do not drop pagetables when empty
Date: Thu, 15 Jun 2017 08:31:23 +0200 [thread overview]
Message-ID: <20170615063123.GA32520@kroah.com> (raw)
In-Reply-To: <87a859ztll.fsf@intel.com>
On Thu, Jun 15, 2017 at 08:51:34AM +0300, Jani Nikula wrote:
> On Wed, 14 Jun 2017, Eric Blau <eblau@eblau.com> wrote:
> > Can the following patch please be included in the next stable release?
> > It looks like it was submitted previously by Daniel Vetter, but has not
> > been included in 4.11.y yet. Thanks.
>
> The previous submission would be [1]. Please reference that instead of
> resending patches with incomplete upstream references. Thank you.
>
> BR,
> Jani.
>
>
> [1] http://mid.mail-archive.com/20170526082906.8982-1-daniel.vetter@ffwll.ch
Ugh, this one flew right by me, and I never even caught it. And that
was because it was sent To: the intel-gfx list, and only had a cc: for
stable, much like all of the other i915 stable patches that you all want
in stable trees, but are not yet included in your tree.
So thanks for the reminder, I'll go pull the original one in now.
greg k-h
next prev parent reply other threads:[~2017-06-15 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 17:07 [Intel-gfx] [PATCH] drm/i915: Do not drop pagetables when empty Eric Blau
2017-06-15 5:51 ` Jani Nikula
2017-06-15 6:31 ` Greg KH [this message]
2017-06-15 6:55 ` Jani Nikula
2017-06-15 7:12 ` Greg KH
2017-06-15 7:40 ` Jani Nikula
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=20170615063123.GA32520@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=eblau@eblau.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=michal.winiarski@intel.com \
--cc=michel.thierry@intel.com \
--cc=mika.kuoppala@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