[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120523151405.f264a88ca4edf8d22c08c86c@canb.auug.org.au>
Date: Wed, 23 May 2012 15:14:05 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [git pull] signals, the first series
Hi Al,
On Tue, 22 May 2012 18:06:35 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Tue, 22 May 2012 05:35:25 +0100 Al Viro <viro@...IV.linux.org.uk> wrote:
> >
> > This is just the first part of the queue (about a half of it);
> > assorted fixes all over the place in signals' handling. This one ends
> > with all sigsuspend() implementations switched to generic one
> > (->saved_sigmask-based), a bunch of assorted old buglets fixed and most
> > of the missing bits of NOTIFY_RESUME hookup in place (two more sit in
> > arm and um trees resp. and there's a couple of broken ones that need
> > obvious fixes - parisc and avr32 check TIF_NOTIFY_RESUME only on one of
> > two codepaths; that'll go in the next series). Please, pull from
> > git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal.git for-linus
>
> I am pretty sure that none of this has been in linux-next ... I have no
> idea what sort of conflicts it will produce with the rest of the code in
> there or what issues that giving it some time in linux-next may discover.
OK, it seem that most of this has been in Andrew's tree for a while,
sorry about that.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists