From: Yin Kangkai <kangkai.yin@linux.intel.com>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH 8/9] udevadm-trigger: add short options in Usage
Date: Wed, 28 Jul 2010 03:17:37 +0000 [thread overview]
Message-ID: <20100728031737.GH29131@kai-debian> (raw)
From 16c72cce078464ba2f62ecf3297c6d6aae78a1cd Mon Sep 17 00:00:00 2001
From: Yin Kangkai <kangkai.yin@intel.com>
Date: Wed, 28 Jul 2010 10:24:48 +0800
Subject: [PATCH 8/9] udevadm-trigger: add short options in Usage
Signed-off-by: Yin Kangkai <kangkai.yin@intel.com>
---
udev/udevadm-trigger.c | 32 ++++++++++++++++----------------
1 files changed, 16 insertions(+), 16 deletions(-)
diff --git a/udev/udevadm-trigger.c b/udev/udevadm-trigger.c
index 481e9cf..0d82606 100644
--- a/udev/udevadm-trigger.c
+++ b/udev/udevadm-trigger.c
@@ -181,22 +181,22 @@ int udevadm_trigger(struct udev *udev, int argc, char *argv[])
break;
case 'h':
printf("Usage: udevadm trigger OPTIONS\n"
- " --verbose print the list of devices while running\n"
- " --dry-run do not actually trigger the events\n"
- " --type= type of events to trigger\n"
- " devices sys devices (default)\n"
- " subsystems sys subsystems and drivers\n"
- " failed trigger only the events which have been\n"
- " marked as failed during a previous run\n"
- " --action=<action> event action value, default is \"change\"\n"
- " --subsystem-match=<subsystem> trigger devices from a matching subsystem\n"
- " --subsystem-nomatch=<subsystem> exclude devices from a matching subsystem\n"
- " --attr-match=<file[=<value>]> trigger devices with a matching attribute\n"
- " --attr-nomatch=<file[=<value>]> exclude devices with a matching attribute\n"
- " --property-match=<key>=<value> trigger devices with a matching property\n"
- " --tag-match=<key>=<value> trigger devices with a matching property\n"
- " --sysname-match=<name> trigger devices with a matching name\n"
- " --help\n\n");
+ " -v, --verbose print the list of devices while running\n"
+ " -n, --dry-run do not actually trigger the events\n"
+ " -t, --type= type of events to trigger\n"
+ " devices sys devices (default)\n"
+ " subsystems sys subsystems and drivers\n"
+ " failed trigger only the events which have been\n"
+ " marked as failed during a previous run\n"
+ " -c, --action=<action> event action value, default is \"change\"\n"
+ " -s, --subsystem-match=<subsystem> trigger devices from a matching subsystem\n"
+ " -S, --subsystem-nomatch=<subsystem> exclude devices from a matching subsystem\n"
+ " -a, --attr-match=<file[=<value>]> trigger devices with a matching attribute\n"
+ " -A, --attr-nomatch=<file[=<value>]> exclude devices with a matching attribute\n"
+ " -p, --property-match=<key>=<value> trigger devices with a matching property\n"
+ " -g, --tag-match=<key>=<value> trigger devices with a matching property\n"
+ " -y, --sysname-match=<name> trigger devices with a matching name\n"
+ " -h, --help\n\n");
goto exit;
default:
goto exit;
--
1.6.5
reply other threads:[~2010-07-28 3:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100728031737.GH29131@kai-debian \
--to=kangkai.yin@linux.intel.com \
--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).