Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Liu <net147@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] udev: fix stopping execution of udev events in init.d script
Date: Fri, 27 Jul 2012 23:51:56 +1000	[thread overview]
Message-ID: <1343397117-1864-1-git-send-email-net147@gmail.com> (raw)

Signed-off-by: Jonathan Liu <net147@gmail.com>
---
 package/udev/S10udev | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/package/udev/S10udev b/package/udev/S10udev
index 70a7c34..13dfdf5 100755
--- a/package/udev/S10udev
+++ b/package/udev/S10udev
@@ -34,7 +34,7 @@ case "$1" in
         ;;
     stop)
         # Stop execution of events
-        udevadm control --stop_exec_queue
+        udevadm control --stop-exec-queue
         killall udevd
         ;;
     *)
-- 
1.7.11.2

             reply	other threads:[~2012-07-27 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 13:51 Jonathan Liu [this message]
2012-07-27 13:51 ` [Buildroot] [PATCH 2/2] udev: use /dev if udev_root not defined in init.d script Jonathan Liu
2012-07-30 20:19   ` Thomas Petazzoni
2012-07-30 20:19 ` [Buildroot] [PATCH 1/2] udev: fix stopping execution of udev events " Thomas Petazzoni

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=1343397117-1864-1-git-send-email-net147@gmail.com \
    --to=net147@gmail.com \
    --cc=buildroot@busybox.net \
    /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