lkml.org 
[lkml]   [2012]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: linux-next: manual merge of the signal tree with the arm-current tree
On Thu, Jul 05, 2012 at 05:35:26PM +1000, Stephen Rothwell wrote:
> Hi Al,
>
> Today's linux-next merge of the signal tree got a conflict in
> arch/arm/kernel/signal.c between commit f73e2ca64281 ("ARM: 7443/1:
> Revert "new way of handling ERESTART_RESTARTBLOCK"") from the arm-current
> tree and commits 9c802c169f96 ("arm: deal with handlerless restarts
> without leaving the kernel") and 76c3f4da3ee4 ("arm: get rid of
> TIF_SYSCALL_RESTARTSYS") from the signal tree.
>
> I have no idea how to cope with this. So I have effectively reverted
> commit f73e2ca64281 ("ARM: 7443/1: Revert "new way of handling
> ERESTART_RESTARTBLOCK"") for today (though parts of that commit are also
> implemented by the above signal tree commits).

Currently, bugs have been found with the signal handling updates which
happened during the last merge window.

Will has concerns with Al's proposed fixes for the signal handling.
Unfortunately, Al isn't responding to attempts to discuss this (for
whatever reason), and as we're now at -rc5, we believe Al's patches are
now too complex to go into this stage of -rc.

We have had to find a way forward on this - which means reverting some
of the commits that went in during the previous merge window.

So, your revert to "fix" this isn't a good idea, because it isn't what
will be going to Linus this weekend.

--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:


\
 
 \ /
  Last update: 2012-07-05 10:21    [W:0.049 / U:31.384 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site