From: Al Viro <viro@ZenIV.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Thorsten Glaser <tg@mirbsd.de>,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
Greg Ungerer <gerg@snapgear.com>
Subject: Re: Signal patchset (was: Re: aranym bug, manifests as "ida_remove called for id=13" on recent kernels)
Date: Wed, 15 Dec 2010 10:10:27 +0000 [thread overview]
Message-ID: <20101215101027.GA31097@ZenIV.linux.org.uk> (raw)
In-Reply-To: <AANLkTi=9B-8KN0oiXoiU+KqPt6B8Vs=d7yu9cui-7e1r@mail.gmail.com>
On Sun, Dec 05, 2010 at 12:15:10PM +0100, Geert Uytterhoeven wrote:
> Unless someone objects, I'm inclined to apply Al's patchset, as it improves the
> situation anyway.
>
> OK?
FWIW, there's an m68knommu counterpart (ACKed by gerg a while ago). The
entire bunch is on ftp.linux.org.uk/pub/people/viro/m68k-signals - both m68k
and m68knommu sets. I don't know how you guys would prefer it done, since
there's a trivial dependency between m68k and m68knommu parts of series -
the former has
+#ifndef __uClinux__
+#define __ARCH_WANT_SYS_RT_SIGSUSPEND
+#endif
in unistd.h and the latter does
-#ifndef __uClinux__
#define __ARCH_WANT_SYS_RT_SIGSUSPEND
-#endif
Both parts switch to generic sys_rt_sigsuspend(), for mmu and nommu resp.,
so they need __ARCH_WANT_SYS_RT_SIGSUSPEND defined as soon as conversion
is done. Other than that they are independent.
next prev parent reply other threads:[~2010-12-15 10:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 11:15 Signal patchset (was: Re: aranym bug, manifests as "ida_remove called for id=13" on recent kernels) Geert Uytterhoeven
2010-12-15 10:10 ` Al Viro [this message]
2010-12-16 13:23 ` Signal patchset Greg Ungerer
2010-12-16 13:23 ` Greg Ungerer
2011-01-06 20:42 ` Geert Uytterhoeven
2011-01-07 10:05 ` Greg Ungerer
2011-01-07 10:05 ` Greg Ungerer
2011-01-07 13:17 ` Geert Uytterhoeven
2011-01-11 0:13 ` Greg Ungerer
2011-01-11 0:13 ` Greg Ungerer
2011-01-01 19:40 ` Thorsten Glaser
2011-01-07 13:21 ` Geert Uytterhoeven
2011-01-09 22:14 ` Thorsten Glaser
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=20101215101027.GA31097@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=tg@mirbsd.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.