From: Ralf Baechle <ralf@linux-mips.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: David Howells <dhowells@redhat.com>,
linux-mips@linux-mips.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix breakage in MIPS siginfo handling
Date: Tue, 19 Mar 2013 19:19:27 +0100 [thread overview]
Message-ID: <20130319181927.GA10535@linux-mips.org> (raw)
In-Reply-To: <20130319150530.GH21522@ZenIV.linux.org.uk>
On Tue, Mar 19, 2013 at 03:05:30PM +0000, Al Viro wrote:
> ACKed-by: Al Viro <viro@zeniv.linux.org.uk>
>
> but I think it should go via mips tree (or straight to Linus, for that
> matter). I can apply it in signal.git and push it to Linus today, though...
I've applied it to my tree. Since I applied a number of other 3.9 fixes
I'm going to wait for another day before sending out a pull request to
Linus.
Thanks,
Ralf
prev parent reply other threads:[~2013-03-19 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 15:00 [PATCH] Fix breakage in MIPS siginfo handling David Howells
2013-03-19 15:05 ` Al Viro
2013-03-19 18:19 ` 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=20130319181927.GA10535@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=stable@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).