linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Cc: LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>,
	Ulrich Drepper <drepper-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Roland McGrath <roland-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Oleg Nesterov <oleg-6lXkIZvqkOAvJsYlp49lxw@public.gmane.org>,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC patch 0/3] signals: add rt_tgsigqueueinfo syscall V2
Date: Thu, 2 Oct 2008 10:57:38 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0810021055400.5549@apollo.tec.linutronix.de> (raw)
In-Reply-To: <cfd18e0f0810010757j7a9f6deaj47a06f30e371af1e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed, 1 Oct 2008, Michael Kerrisk wrote:
> [CC+=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org]
> 
> On Wed, Oct 1, 2008 at 12:01 PM, Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org> wrote:
> > Changes vs. V1: compat_sys_rt_sigqueueinfo implemented. Thanks Roland !
> >
> > sys_kill has a counterpart sys_tgkill which allows to send signals to
> > a particular thread. sys_rt_sigqueueinfo is lacking such a counterpart.
> >
> > Aside of the asymetry it is a show stopper for migrating applications
> > from other unix-alike RTOSes.
> >
> > The following patch series implements rt_tgsigqueueinfo and hooks it
> > up for x86.
> 
> This is an excellent candidate for CCing to the new linux-api@vger
> (http://thread.gmane.org/gmane.linux.ltp/5658/), since it is an API
> change.

Oops, yes forgot about that.
 
> > Find below the raw documentation.
> 
> Thanks -- I'll work that up into a man page when this gets closer to release.

I'll send out test code later this week - once I get a breather from
bugs and regressions again.

Thanks,

	tglx

--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-10-02  8:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081001095204.343984413@linutronix.de>
     [not found] ` <20081001095204.343984413-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2008-10-01 14:57   ` [RFC patch 0/3] signals: add rt_tgsigqueueinfo syscall V2 Michael Kerrisk
     [not found]     ` <cfd18e0f0810010757j7a9f6deaj47a06f30e371af1e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-02  8:57       ` Thomas Gleixner [this message]
     [not found]         ` <alpine.LFD.1.10.0810021055400.5549-dbfLifZv8x0yMciVaGeJ0d53zsg1cpMQ@public.gmane.org>
2008-10-08  9:49           ` Michael Kerrisk

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=alpine.LFD.1.10.0810021055400.5549@apollo.tec.linutronix.de \
    --to=tglx-hfztesqfncyowbw4kg4ksq@public.gmane.org \
    --cc=drepper-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mingo-X9Un+BFzKDI@public.gmane.org \
    --cc=mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
    --cc=oleg-6lXkIZvqkOAvJsYlp49lxw@public.gmane.org \
    --cc=roland-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).