stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Paul Burton <paul.burton@mips.com>
Cc: linux-mips@linux-mips.org, James Hogan <jhogan@kernel.org>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH] MIPS: Schedule on CPUs we need to lose FPU for a mode switch
Date: Wed, 20 Dec 2017 12:15:25 +0100	[thread overview]
Message-ID: <20171220111525.GF28538@linux-mips.org> (raw)
In-Reply-To: <20171219235047.14382-1-paul.burton@mips.com>

On Tue, Dec 19, 2017 at 03:50:47PM -0800, Paul Burton wrote:

Looks good but doesn't apply on top of my 4.15-fixes branch which as of
now is at b67336eee3fc ("MIPS: Validate PR_SET_FP_MODE prctl(2) requests
against the ABI of the task").  See [1].

Can you respin?

Thanks,

  Ralf

[1] https://git.linux-mips.org/cgit/ralf/upstream-sfr.git/commit/?id=b67336eee3fcb8ecedc6c13e2bf88aacfa3151e2

      reply	other threads:[~2017-12-20 11:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 23:50 [PATCH] MIPS: Schedule on CPUs we need to lose FPU for a mode switch Paul Burton
2017-12-20 11:15 ` Ralf Baechle [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=20171220111525.GF28538@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=jhogan@kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=paul.burton@mips.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;
as well as URLs for NNTP newsgroup(s).