Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: James Hogan <james.hogan@mips.com>,
	Paul Burton <Paul.Burton@mips.com>,
	Alex Smith <alex@alex-smith.me.uk>,
	Dave Martin <Dave.Martin@arm.com>,
	linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 0/6] MIPS: NT_PRFPREG regset handling fixes
Date: Tue, 12 Dec 2017 19:55:32 +0100	[thread overview]
Message-ID: <20171212185532.GA5131@linux-mips.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1712111833360.4584@tp.orcam.me.uk>

Thanks, applied.

  Ralf

      parent reply	other threads:[~2017-12-12 18:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 22:50 [PATCH v2 0/6] MIPS: NT_PRFPREG regset handling fixes Maciej W. Rozycki
2017-12-11 22:50 ` Maciej W. Rozycki
2017-12-11 22:51 ` [PATCH v2 1/6] MIPS: Factor out NT_PRFPREG regset access helpers Maciej W. Rozycki
2017-12-11 22:51   ` Maciej W. Rozycki
2017-12-11 22:52 ` [PATCH v2 2/6] MIPS: Guard against any partial write attempt with PTRACE_SETREGSET Maciej W. Rozycki
2017-12-11 22:52   ` Maciej W. Rozycki
2017-12-11 22:53 ` [PATCH v2 3/6] MIPS: Consistently handle buffer counter " Maciej W. Rozycki
2017-12-11 22:53   ` Maciej W. Rozycki
2017-12-11 22:54 ` [PATCH v2 4/6] MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA Maciej W. Rozycki
2017-12-11 22:54   ` Maciej W. Rozycki
2017-12-11 22:55 ` [PATCH v2 5/6] MIPS: Also verify sizeof `elf_fpreg_t' with PTRACE_SETREGSET Maciej W. Rozycki
2017-12-11 22:55   ` Maciej W. Rozycki
2017-12-11 22:56 ` [PATCH v2 6/6] MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses Maciej W. Rozycki
2017-12-11 22:56   ` Maciej W. Rozycki
2017-12-12 18:55 ` 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=20171212185532.GA5131@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Dave.Martin@arm.com \
    --cc=Paul.Burton@mips.com \
    --cc=alex@alex-smith.me.uk \
    --cc=james.hogan@mips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@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