From: David Woodhouse <dwmw2@infradead.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Roland McGrath <roland@redhat.com>,
"Linus Torvalds <torvalds@linux-foundation.org>Andrew Morton"
<akpm@linux-foundation.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-s390@vger.kernel.org, tony.luck@intel.com,
linux-ia64@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, miles@gnu.org,
geert@linux-m68k.org, zippel@linux-m68k.org
Subject: Re: [PATCH 1/2] HAVE_SET_RESTORE_SIGMASK
Date: Fri, 11 Apr 2008 13:40:34 +0000 [thread overview]
Message-ID: <1207921234.22291.4.camel@pmac.infradead.org> (raw)
In-Reply-To: <20080410203250.GA21589@flint.arm.linux.org.uk>
On Thu, 2008-04-10 at 21:32 +0100, Russell King wrote:
> On Wed, Apr 09, 2008 at 12:45:32PM +0100, David Woodhouse wrote:
> > On Fri, 2008-03-28 at 20:11 -0700, Roland McGrath wrote:
> > > Change all the #ifdef TIF_RESTORE_SIGMASK conditionals in non-arch
> > > code to #ifdef HAVE_SET_RESTORE_SIGMASK.
> >
> > That ifdef was only supposed to be a temporary thing until all
> > architectures had implemented TIF_RESTORE_SIGMASK anyway.
> >
> > It looks like only ARM, v850 and m68k which are still missing it; if
> > those three architectures can catch up, then hopefully it can die off
> > completely quite soon.
>
> Well, we don't have the pselect/ppoll/epoll_wait syscalls and there's
> been no demand for them, so I don't particularly see the point of
> going to the trouble of adding support for something no one's
> interested in using.
You're not likely to see demand for it from users. I believe glibc will
emulate it as best it can (which is not very well), and things will
appear to work.... most of the time.
--
dwmw2
next prev parent reply other threads:[~2008-04-11 13:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 0:12 [PATCH 1/4] set_restore_sigmask Roland McGrath
2008-03-29 0:13 ` [PATCH 2/4] set_restore_sigmask TIF_SIGPENDING Roland McGrath
2008-03-29 0:53 ` Linus Torvalds
2008-03-29 2:24 ` Roland McGrath
2008-03-29 2:52 ` Linus Torvalds
2008-03-29 3:12 ` Roland McGrath
2008-03-29 3:11 ` [PATCH 1/2] HAVE_SET_RESTORE_SIGMASK Roland McGrath
2008-04-09 11:45 ` David Woodhouse
2008-04-10 20:32 ` Russell King
2008-04-11 13:40 ` David Woodhouse [this message]
2008-03-29 3:14 ` Roland McGrath
2008-03-29 3:14 ` [PATCH 2/2] x86 TS_RESTORE_SIGMASK Roland McGrath
2008-03-31 13:01 ` Ingo Molnar
2008-03-31 19:30 ` Roland McGrath
2008-03-30 10:53 ` [PATCH 2/4] set_restore_sigmask TIF_SIGPENDING Paul Mackerras
2008-04-08 11:35 ` Oleg Nesterov
2008-04-08 14:53 ` Linus Torvalds
2008-04-08 19:51 ` Roland McGrath
2008-04-09 11:16 ` David Woodhouse
2008-04-09 11:39 ` Oleg Nesterov
2008-04-09 12:57 ` Petr Tesarik
2008-04-09 16:14 ` David Woodhouse
2008-04-09 16:22 ` Oleg Nesterov
2008-04-09 18:40 ` David Woodhouse
2008-03-29 0:14 ` [PATCH 3/4] s390 renumber TIF_RESTORE_SIGMASK Roland McGrath
2008-03-31 7:53 ` Martin Schwidefsky
2008-03-29 0:14 ` [PATCH 4/4] ia64 " Roland McGrath
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=1207921234.22291.4.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=miles@gnu.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=roland@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=tony.luck@intel.com \
--cc=zippel@linux-m68k.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