diff options
author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-11-02 14:27:23 -0500 |
---|---|---|
committer | Anthony G. Basile <blueness@gentoo.org> | 2014-11-02 14:27:23 -0500 |
commit | ad9c47a35be27d0684066562ebcc083329c2a080 (patch) | |
tree | a272b495e6e4e6ea49101e6275b1222a52262265 /src/libudev | |
parent | 66498b0110dc8966a1d98a450249de26559fd495 (diff) |
Use log "level" instead of "priority"
The term "priority" is misleading because higher levels have lower
priority. "Level" is clearer and shorter.
This commit touches only the textual descriptions, not function and variable
names themselves. "Priority" is used in various command-line switches and
protocol constants, so completly getting rid of "priority" is hard.
I also left "priority" in various places where the clarity suffered
when it was removed.
Signed-off-by: Anthony G. Basile <blueness@gentoo.org>
Diffstat (limited to 'src/libudev')
-rw-r--r-- | src/libudev/libudev.c | 20 |
1 files changed, 9 insertions, 11 deletions
diff --git a/src/libudev/libudev.c b/src/libudev/libudev.c index 5d3ad50411..2c18c7e801 100644 --- a/src/libudev/libudev.c +++ b/src/libudev/libudev.c @@ -79,7 +79,7 @@ static void log_stderr(struct udev *udev, * @udev: udev library context * * Retrieve stored data pointer from library context. This might be useful - * to access from callbacks like a custom logging function. + * to access from callbacks like a custom log function. * * Returns: stored userdata **/ @@ -196,7 +196,7 @@ _public_ struct udev *udev_new(void) prio = util_log_priority(val); if (prio < 0) - udev_err(udev, "/etc/udev/udev.conf:%u: invalid logging level '%s', ignoring.\n", line_nr, val); + udev_err(udev, "/etc/udev/udev.conf:%u: invalid log level '%s', ignoring.\n", line_nr, val); else udev_set_log_priority(udev, prio); continue; @@ -247,11 +247,11 @@ _public_ struct udev *udev_unref(struct udev *udev) /** * udev_set_log_fn: * @udev: udev library context - * @log_fn: function to be called for logging messages + * @log_fn: function to be called for log messages * * The built-in logging writes to stderr. It can be * overridden by a custom function, to plug log messages - * into the users' logging functionality. + * into the users' log functionality. * **/ _public_ void udev_set_log_fn(struct udev *udev, @@ -260,17 +260,16 @@ _public_ void udev_set_log_fn(struct udev *udev, const char *format, va_list args)) { udev->log_fn = log_fn; - udev_dbg(udev, "custom logging function %p registered\n", log_fn); + udev_dbg(udev, "custom log function %p registered\n", log_fn); } /** * udev_get_log_priority: * @udev: udev library context * - * The initial logging priority is read from the udev config file - * at startup. + * The initial log level is read from the udev config file at startup. * - * Returns: the current logging priority + * Returns: the current log level **/ _public_ int udev_get_log_priority(struct udev *udev) { @@ -280,10 +279,9 @@ _public_ int udev_get_log_priority(struct udev *udev) /** * udev_set_log_priority: * @udev: udev library context - * @priority: the new logging priority + * @priority: the new log priority * - * Set the current logging priority. The value controls which messages - * are logged. + * Set the log level. This value controls which messages are logged. **/ _public_ void udev_set_log_priority(struct udev *udev, int priority) { |