From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Dmitry Antipov" <antipov@dev.rtsoft.ru>
Cc: "Robert Love" <rlove@google.com>,
"John McCutchan" <ttb@tentacle.dhs.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: inotify SIGIO documentation for inotify.7 man page
Date: Mon, 28 Apr 2008 13:45:50 +0200 [thread overview]
Message-ID: <cfd18e0f0804280445v3bc153d9pfeb8dbdae6270447@mail.gmail.com> (raw)
In-Reply-To: <47FA9D29.3080200@gmail.com>
Hey Dmitry,
Ping!
Cheers,
Michael
On Tue, Apr 8, 2008 at 12:16 AM, Michael Kerrisk
<mtk.manpages@googlemail.com> wrote:
> Hi Dmitry,
>
> I don't think I got notification of the 2.6.25 API change to inotify from
> you. Please CC me on API changes.
>
> The following is my attempt to document the SIGIO feature that is new in
> 2.6.25. Does this look okay to you?
>
> Since Linux 2.6.25, signal-driven I/O notification is
> available for inotify file descriptors; see the discus-
> sion of F_SETFL (for setting the O_ASYNC flag), F_SETOWN,
> and F_SETSIG in fcntl(2). The siginfo_t structure
> (described in sigaction(2)) that is passed to the signal
> handler has the following fields set: si_fd is set to the
> inotify file descriptor number; si_signo is set to the
> signal number; si_code is set to POLL_IN; and POLLIN is
> set in si_band.
>
> Cheers,
>
> Michael
>
> --
> Michael Kerrisk
> Maintainer of the Linux man-pages project
> http://www.kernel.org/doc/man-pages/
> Want to report a man-pages bug? Look here:
> http://www.kernel.org/doc/man-pages/reporting_bugs.html
>
>
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
prev parent reply other threads:[~2008-04-28 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 22:16 inotify SIGIO documentation for inotify.7 man page Michael Kerrisk
2008-04-28 11:45 ` Michael Kerrisk [this message]
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=cfd18e0f0804280445v3bc153d9pfeb8dbdae6270447@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=antipov@dev.rtsoft.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@google.com \
--cc=ttb@tentacle.dhs.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).