nvme: Use fprintf for error message logging in get_log()

perror uses the errno variable which is likely set to 0, which leads to
error messages like

  non-zero log-len is required param: Success

Use fprintf and write to stderr the error messages.

Signed-off-by: Daniel Wagner <dwagner@suse.de>

diff --git a/nvme.c b/nvme.c
index e10e3823d0ff94b2568645645fb5822a7209f447..b76df8521edc0bfc898260c139b10736ff600898 100644 (file)
--- a/nvme.c
+++ b/nvme.c
@@ -2179,19 +2179,19 @@ static int get_log(int argc, char **argv, struct command *cmd, struct plugin *pl
        }
 
        if (!cfg.log_len) {
-               perror("non-zero log-len is required param\n");
+               fprintf(stderr, "non-zero log-len is required param\n");
                err = -EINVAL;
                goto close_dev;
        }
 
        if (cfg.lsp > 128) {
-               perror("invalid lsp param\n");
+               fprintf(stderr, "invalid lsp param\n");
                err = -EINVAL;
                goto close_dev;
        }
 
        if (cfg.uuid_index > 128) {
-               perror("invalid uuid index param\n");
+               fprintf(stderr, "invalid uuid index param\n");
                err = -EINVAL;
                goto close_dev;
        }