From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Helge Deller <deller@gmx.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [git pull] signal.git
Date: Sun, 24 Feb 2013 03:25:27 +0000 [thread overview]
Message-ID: <20130224032527.GT4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFwx-O4Q=1gKgv=cyG8ObzUyPVh9Ctmuh-DX_DE9rumU5g@mail.gmail.com>
On Sat, Feb 23, 2013 at 06:56:02PM -0800, Linus Torvalds wrote:
> On Wed, Feb 20, 2013 at 2:52 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > * a bunch of signal-related syscalls (both native and compat) unified.
>
> Ok, in the meantime I had merged the parisc and powerpc trees, which
> had their own fixes in this area: powerpc added the transactional
> memory support for power8 (which impacted signal save/restore), and
> parisc had some fixes to the routines you then removed in favor of
> generic ones.
>
> I fixed up the conflicts, and they didn't look that bad, but I could
> easily have messed something up, so people - please double-check the
> end result.
Ouch... Lesson for me - before hitting send, check if anything relevant
has arrived while the mail was being written...
next prev parent reply other threads:[~2013-02-24 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 22:52 [git pull] signal.git Al Viro
2013-02-20 22:58 ` Al Viro
2013-02-24 2:56 ` Linus Torvalds
2013-02-24 2:56 ` Linus Torvalds
2013-02-24 3:25 ` Al Viro [this message]
2013-02-24 3:25 ` Al Viro
2013-02-24 14:48 ` Benjamin Herrenschmidt
2013-02-24 23:04 ` James Bottomley
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=20130224032527.GT4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=benh@kernel.crashing.org \
--cc=deller@gmx.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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