linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky-AlSwsSmVLrQ@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Document struct sigevent in sigevent(7)
Date: Wed, 24 Feb 2010 21:15:48 +0100	[thread overview]
Message-ID: <20100224201548.GA19115@machine.or.cz> (raw)
In-Reply-To: <20090920150500.GO3674-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>

On Sun, Sep 20, 2009 at 05:05:00PM +0200, Petr Baudis wrote:
> On Wed, Apr 15, 2009 at 01:14:42PM +0200, Petr Baudis wrote:
> > The sigevent structure is used as a common interface for several
> > asynchronous pthreads functions; also, getaddrinfo_a() uses it
> > and in the future, other library functions might.
> > 
> > Currently, it is completely non-descript in some cases, plus
> > there are two competing descriptions in timer_create(2) and
> > mq_notify(3) (the former appears to be based on the latter).
> > This patch attempts to unify the descriptions in a single
> > manual page and networks it to the rest, so that I do not
> > have to add yet another description for the getaddrinfo_a(3)
> > manual page (currently in the works).
> > 
> > P.S.: There are two unresolved issues with this patch - the
> > timer_create(2) requirement of real-time signal requirements
> > is somewhat confusing and it seems that SIGEV_THREAD_ID can
> > be or'd with SIGEV_SIGNAL or not. I did not have time to research
> > this so far, so I decided to rather send it in and see if someone
> > knows about this off the top of their head.
> > 
> > Signed-off-by: Petr Baudis <pasky-AlSwsSmVLrQ@public.gmane.org>
> 
> Ping...

Ping... :-)

P.S.: I'm sorry that I have not been of any help with maintaining
manpages contrary to what I promised - it turns out I'm currently way
too swamped by other stuff.. :-(

-- 
				Petr "Pasky" Baudis
A great many people think they are thinking when they are merely
rearranging their prejudices. -- William James
--
To unsubscribe from this list: send the line "unsubscribe linux-man" 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:[~2010-02-24 20:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 11:14 [PATCH] Document struct sigevent in sigevent(7) Petr Baudis
     [not found] ` <20090415111442.GN8940-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>
2009-09-20 15:05   ` Petr Baudis
     [not found]     ` <20090920150500.GO3674-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>
2010-02-24 20:15       ` Petr Baudis [this message]
2010-09-19 16:23   ` Michael Kerrisk
     [not found]     ` <AANLkTin1o4JQ98zmsox6Qg9R5oaPCswieATTd98rCSjY-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-19 16:31       ` Michael Kerrisk
2010-09-21 15:31       ` Petr Baudis

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=20100224201548.GA19115@machine.or.cz \
    --to=pasky-alswssmvlrq@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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).