public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: no_spam@ntlworld.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: kill_fasync usage
Date: Tue, 04 Mar 2003 22:02:14 +0100	[thread overview]
Message-ID: <3E651456.1050808@colorfullife.com> (raw)

SA wrote:

>I wnat to use kill_fasync(struct fasync_struct *PTR,...) to notify userland of 
>events.  Can I just call kill_fasync regardless of the state of PTR or does 
>PTR actually have to point to something valid.  
>  
>
kill_fasync receives the _address_ of the variable that contains the 
list of processes that need notifications. It must not be NULL. (I 
assume you look at 2.4 or 2.5 - 2.2 had a different interface)

Check linux/drivers/char/busmouse.c for an example, the interface is 
simple: call fasync_helper to register and kill_fasync for the actual 
notification.

--
    Manfred


             reply	other threads:[~2003-03-04 20:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 21:02 Manfred Spraul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-04 20:08 kill_fasync usage no_spam

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=3E651456.1050808@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=no_spam@ntlworld.com \
    /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