From: Andrew Morton <akpm@osdl.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Kernel thread signal handling.
Date: Mon, 13 Oct 2003 05:11:49 -0700 [thread overview]
Message-ID: <20031013051149.29da705a.akpm@osdl.org> (raw)
In-Reply-To: <1066046102.14783.11.camel@hades.cambridge.redhat.com>
David Woodhouse <dwmw2@infradead.org> wrote:
>
> > How does userspace identify the JFFS2 process to which to send the
> > signal?
>
> daemonize("jffs2_gcd_mtd%d", c->mtd->index);
And then what? Parse the output of ps(1)? Use pidof(8)?
> Bitching accomplished; now can we fix the bug?
Insufficient contrition detected :)
Why cannot a procfs or sysfs control be used?
next prev parent reply other threads:[~2003-10-13 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 10:31 [RFC][PATCH] Kernel thread signal handling David Woodhouse
2003-10-13 11:02 ` Andrew Morton
2003-10-13 11:08 ` Russell King
2003-10-13 11:29 ` David Woodhouse
2003-10-13 11:21 ` David Woodhouse
2003-10-13 11:40 ` Andrew Morton
2003-10-13 11:55 ` David Woodhouse
2003-10-13 12:11 ` Andrew Morton [this message]
2003-10-13 12:30 ` David Woodhouse
2003-10-13 16:36 ` Linus Torvalds
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=20031013051149.29da705a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.