From: Ralf Baechle <ralf@linux-mips.org>
To: James Hogan <james.hogan@imgtec.com>
Cc: Gregory Fong <gregory.0xf0@gmail.com>,
linux-mips@linux-mips.org, stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: stack protector: Fix per-task canary switch
Date: Mon, 7 Oct 2013 14:48:59 +0200 [thread overview]
Message-ID: <20131007124859.GF3098@linux-mips.org> (raw)
In-Reply-To: <1381144466-19736-1-git-send-email-james.hogan@imgtec.com>
On Mon, Oct 07, 2013 at 12:14:26PM +0100, James Hogan wrote:
> Ralf: This is a regression in v3.11, so please consider for v3.12.
Applied, will send to Linus with the next pull request.
stable folks - please apply to 3.12-stable.
Thanks!
Ralf
next prev parent reply other threads:[~2013-10-07 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 11:14 [PATCH] MIPS: stack protector: Fix per-task canary switch James Hogan
2013-10-07 11:14 ` James Hogan
2013-10-07 12:48 ` Ralf Baechle [this message]
2013-10-10 23:16 ` Greg KH
2013-10-14 8:40 ` James Hogan
2013-10-14 8:40 ` James Hogan
2013-10-14 10:27 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2013-10-07 11:08 James Hogan
2013-10-07 11:08 ` James Hogan
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=20131007124859.GF3098@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=gregory.0xf0@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=linux-mips@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