linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev_rules_get_run confusion
Date: Thu, 26 Jan 2006 17:40:54 +0000	[thread overview]
Message-ID: <200601262040.56808.arvidjaar@mail.ru> (raw)
In-Reply-To: <200601252342.15059.arvidjaar@mail.ru>


[-- Attachment #1.1: Type: text/plain, Size: 332 bytes --]

On Thursday 26 January 2006 04:57, Kay Sievers wrote:
> On Wed, Jan 25, 2006 at 11:42:14PM +0300, Andrey Borzenkov wrote:
> > What this function does? As it is now it does *not* get called at all.
>

Oops I should never post that late. I missed this piece in previous patch. 
Trivial one-liner follows.

regards

-andrey

[-- Attachment #1.2: remove_apply_from_get_run.diff --]
[-- Type: text/x-diff, Size: 815 bytes --]

Subject: [PATCH] Remove udev_rules_apply_format from udev_rules_get_run

From: Andrey Borzenkov <arvidjaar@mail.ru>

This removes now redundant substitution (otherwise it will be expanded
twice).

Signed-off-by: Andrey Borzenkov <arvidjaar@mail.ru>
---

 udev_rules.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/udev_rules.c b/udev_rules.c
index 90dc024..5d68728 100644
--- a/udev_rules.c
+++ b/udev_rules.c
@@ -1082,7 +1082,6 @@ int udev_rules_get_run(struct udev_rules
 					name_list_cleanup(&udev->run_list);
 				}
 				strlcpy(program, key_val(rule, &rule->run), sizeof(program));
-				udev_rules_apply_format(udev, program, sizeof(program));
 				dbg("add run '%s'", program);
 				name_list_add(&udev->run_list, program, 0);
 				if (rule->run.operation == KEY_OP_ASSIGN_FINAL)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-01-26 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-25 20:42 udev_rules_get_run confusion Andrey Borzenkov
2006-01-26  1:57 ` Kay Sievers
2006-01-26 17:40 ` Andrey Borzenkov [this message]
2006-01-26 23:12 ` Kay Sievers

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=200601262040.56808.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --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 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).