From: Christoph Hellwig <hch@lst.de>
To: Chaitanya Kulkarni <kch@nvidia.com>
Cc: linux-nvme@lists.infradead.org, kbusch@kernel.org, hch@lst.de,
sagi@grimberg.me, alan.adamson@oracle.com
Subject: Re: [PATCH V6 1/1] nvme: allow passthru cmd error logging
Date: Wed, 2 Aug 2023 14:01:58 +0200 [thread overview]
Message-ID: <20230802120158.GA30301@lst.de> (raw)
In-Reply-To: <20230629011713.28554-2-kch@nvidia.com>
> +
> + if (ctrl->passthru_log_err)
> + return sysfs_emit(buf, "on\n");
> +
> + return sysfs_emit(buf, "off\n");
return sysfs_emit(buf, ctrl->passthru_log_err ? "on" : "off");
> +}
> +
> +static ssize_t nvme_passthru_err_log_store(struct device *dev,
> + struct device_attribute *attr, const char *buf, size_t count)
> +{
> + struct nvme_ctrl *ctrl = dev_get_drvdata(dev);
> + int passthru_enable, err;
> +
> + err = kstrtoint(buf, 10, &passthru_enable);
> + if (err)
> + return -EINVAL;
> +
> + switch (passthru_enable) {
> + case true:
> + case false:
> + ctrl->passthru_log_err = passthru_enable;
> + break;
> + default:
> + pr_err("invlid value %d for admin error logging [on:1 off:0]\n",
> + passthru_enable);
> + break;
> + }
> + return count;
This should use kstrtobool.
Also I thik the flag feels a bit too sparse. Why not
something like passthru_err_log_enabled that explains what it does?
next prev parent reply other threads:[~2023-08-02 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 1:17 [PATCH V6 0/1] nvme: allow passthru cmd error logging Chaitanya Kulkarni
2023-06-29 1:17 ` [PATCH V6 1/1] " Chaitanya Kulkarni
2023-08-02 12:01 ` Christoph Hellwig [this message]
2023-08-02 17:14 ` Chaitanya Kulkarni
2023-08-01 3:29 ` [PATCH V6 0/1] " Chaitanya Kulkarni
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=20230802120158.GA30301@lst.de \
--to=hch@lst.de \
--cc=alan.adamson@oracle.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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