linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Hugh Dickins <hughd@google.com>,
	Jani Nikula <jani.nikula@intel.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	chris@chris-wilson.co.uk, daniel.vetter@ffwll.ch,
	linux-kernel@vger.kernel.org
Subject: Re: Q. drm/i915 shrinker, synchronize_rcu_expedited() from handlers
Date: Thu, 15 Jun 2017 08:05:21 +0900	[thread overview]
Message-ID: <9211.1497481521@jrobl> (raw)
In-Reply-To: <1496215621.4267.2.camel@linux.intel.com>

Joonas Lahtinen:
> Don't worry, it's not lost. It was merged to drm-intel-fixes and thus is in the pipeline.
>
> There were some unexpected delays getting fixes in, sorry for that.

Thanx, I got linux-v4.12-rc4 and it contains
	4681ee2 2017-05-18 drm/i915: Do not sync RCU during shrinking

How about v4.11.x series?
I got v4.11.5, but it doesn't contain the fix.
Do you have a plan?


J. R. Okajima

  reply	other threads:[~2017-06-14 23:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30  6:07 Q. drm/i915 shrinker, synchronize_rcu_expedited() from handlers J. R. Okajima
2017-04-30  9:43 ` Andrea Arcangeli
2017-05-01  2:05   ` J. R. Okajima
2017-05-05  9:39     ` Joonas Lahtinen
2017-05-05 21:57       ` Hugh Dickins
2017-05-08  8:04         ` Joonas Lahtinen
2017-05-10  3:04           ` Hugh Dickins
2017-05-10  9:54             ` Joonas Lahtinen
2017-05-10 10:43             ` Andrea Arcangeli
2017-05-10 11:01               ` Joonas Lahtinen
2017-05-05 23:28       ` J. R. Okajima
2017-05-20  1:56         ` J. R. Okajima
2017-05-22  6:02           ` Joonas Lahtinen
2017-05-30 20:00             ` Hugh Dickins
2017-05-31  7:10               ` Jani Nikula
2017-05-31  7:27               ` Joonas Lahtinen
2017-06-14 23:05                 ` J. R. Okajima [this message]
2017-06-15  7:07                   ` Jani Nikula
2017-06-26 23:15                     ` J. R. Okajima

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=9211.1497481521@jrobl \
    --to=hooanon05g@gmail.com \
    --cc=aarcange@redhat.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=hughd@google.com \
    --cc=jani.nikula@intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).