linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
	imunsie@au1.ibm.com, linuxppc-dev@lists.ozlabs.org
Cc: stable@vger.kernel.org
Subject: Re: cxl: Fix struct pid leak when attaching a process through user API
Date: Tue, 26 Jan 2016 09:16:09 +0100	[thread overview]
Message-ID: <56A72B49.6040104@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160126031102.1CE27140317@ozlabs.org>



Le 26/01/2016 04:11, Michael Ellerman a écrit :
> This no longer applies, since we merged 7b8ad495d592 ("cxl: Fix DSI misses when
> the context owning task exits").

Yes, on 4.5, it has been superseded by 7b8ad495d592.
It may still be worth considering for stable releases though.

   Fred

      reply	other threads:[~2016-01-26  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 12:13 [PATCH] cxl: Fix struct pid leak when attaching a process through user API Frederic Barrat
2015-11-03 22:25 ` Ian Munsie
2015-11-03 22:45 ` Andrew Donnellan
2016-01-26  3:11 ` Michael Ellerman
2016-01-26  8:16   ` Frederic Barrat [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=56A72B49.6040104@linux.vnet.ibm.com \
    --to=fbarrat@linux.vnet.ibm.com \
    --cc=imunsie@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --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;
as well as URLs for NNTP newsgroup(s).