stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: stable@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 3.18 v2 0/5] MIPS: NT_PRFPREG regset handling fixes
Date: Sat, 13 Jan 2018 18:41:08 +0100	[thread overview]
Message-ID: <20180113174108.GD25277@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1801111620330.20647@tp.orcam.me.uk>

On Thu, Jan 11, 2018 at 04:53:41PM +0000, Maciej W. Rozycki wrote:
> Hi,
> 
>  This is a repost of my recent 3.18 backports of NT_PRFPREG regset 
> handling fixes, sent as a series for patch ordering clarity.  I've added 
> `v2' annotation for patch management purposes, retaining original 
> headings.  The patches themselves are unchanged.

Thanks for the series, all now applied.

greg k-h

      parent reply	other threads:[~2018-01-13 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 16:53 [PATCH 3.18 v2 0/5] MIPS: NT_PRFPREG regset handling fixes Maciej W. Rozycki
2018-01-11 16:54 ` [PATCH 3.18 v2 1/5] MIPS: Factor out NT_PRFPREG regset access helpers Maciej W. Rozycki
2018-01-11 16:55 ` [PATCH 3.18 v2 2/5] MIPS: Guard against any partial write attempt with PTRACE_SETREGSET Maciej W. Rozycki
2018-01-11 16:55 ` [PATCH 3.18 v2 3/5] MIPS: Consistently handle buffer counter " Maciej W. Rozycki
2018-01-11 16:56 ` [PATCH 3.18 v2 4/5] MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA Maciej W. Rozycki
2018-01-11 16:57 ` [PATCH 3.18 v2 5/5] MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses Maciej W. Rozycki
2018-01-13 17:41 ` Greg KH [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=20180113174108.GD25277@kroah.com \
    --to=greg@kroah.com \
    --cc=macro@mips.com \
    --cc=ralf@linux-mips.org \
    --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).