All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaro Koskinen <aaro.koskinen@iki.fi>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Helge Deller <deller@gmx.de>,
	linux-parisc <linux-parisc@vger.kernel.org>,
	John David Anglin <dave.anglin@bell.net>,
	Jeroen Roovers <jer@gentoo.org>
Subject: Re: systemd on hppa and number of free RT signals
Date: Wed, 8 Oct 2014 01:12:07 +0300	[thread overview]
Message-ID: <20141007221207.GA599@drone.musicnaut.iki.fi> (raw)
In-Reply-To: <CAE2sS1jy4sgs7xSev5-NnVqOqb8nUvQVGnc=JZt=tc-1HPdSgQ@mail.gmail.com>

Hi,

On Tue, Oct 07, 2014 at 05:03:30PM -0400, Carlos O'Donell wrote:
> On Tue, Oct 7, 2014 at 3:39 PM, Helge Deller <deller@gmx.de> wrote:
> > What's your opinion on this?
> 
> Flawless hack. Very well reorganized. Your removal of SIGLOST, and
> reorganizing is the best I could come up with also.
> 
> The only thing I will do different is make SIGEMT equal to SIGABRT,
> that way we preserve the semantics of what this operation means. Linux
> doesn't use SIGEMT, but it keeps hppa defining this for use by other
> software that might want similar semantics. You can catch SIGABRT and
> operate on it, so it's one way forward.
> 
> If you agree I'll checkin to glibc master.

BTW, is there any plan/schedule for getting glibc to support pa-risc
without out-of-tree patches? Any help (e.g. testing) needed there?

A.

  parent reply	other threads:[~2014-10-07 22:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 19:39 systemd on hppa and number of free RT signals Helge Deller
2014-10-07 20:50 ` Jeroen Roovers
2014-10-07 21:07   ` Carlos O'Donell
2014-10-07 21:25   ` Helge Deller
2014-10-07 21:03 ` Carlos O'Donell
2014-10-07 21:21   ` Helge Deller
2014-10-07 22:12   ` Aaro Koskinen [this message]
2014-10-09 20:41   ` Aaro Koskinen
2014-10-09 20:48     ` Carlos O'Donell
2014-10-09 20:58       ` Helge Deller
2014-10-07 22:34 ` Aaro Koskinen
2014-10-08 15:59   ` John David Anglin
2014-10-08  9:10 ` Helge Deller

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=20141007221207.GA599@drone.musicnaut.iki.fi \
    --to=aaro.koskinen@iki.fi \
    --cc=carlos@systemhalted.org \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=jer@gentoo.org \
    --cc=linux-parisc@vger.kernel.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 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.