From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - make exec_callout() reusable
Date: Sat, 10 Jan 2004 01:51:22 +0000 [thread overview]
Message-ID: <20040110015122.GB2137@vrfy.org> (raw)
In-Reply-To: <20040108183355.GB2788@vrfy.org>
On Fri, Jan 09, 2004 at 05:11:14PM -0800, Greg KH wrote:
> On Thu, Jan 08, 2004 at 07:33:55PM +0100, Kay Sievers wrote:
> > Here is a patch that switches exec_callout() to be reusable.
> > I want it to be callable in a different context.
>
> Care to hint about what context that would be? :)
Oh, I dropped the idea. I wanted that some keys are evaluated by a
external program, some sort of a tricky callout.
While thinking about it, the idea for dropping all the explicit methods came up.
The callout method converted to only a PROGRAM= key combinable with every other key
seems the cleaner solution.
But we never know. Maybe some day we need a free callable exec :)
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-10 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 18:33 [PATCH] udev - make exec_callout() reusable Kay Sievers
2004-01-10 1:11 ` Greg KH
2004-01-10 1:51 ` Kay Sievers [this message]
2004-01-10 3:54 ` Greg KH
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=20040110015122.GB2137@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.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.