Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Alan Adamson <alan.adamson@oracle.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	"hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>
Subject: Re: [PATCH V9 1/1] nvme: allow passthru cmd error logging
Date: Wed, 31 Jan 2024 22:54:12 +0000	[thread overview]
Message-ID: <efc53006-6174-484b-8560-fac7b3ad3448@nvidia.com> (raw)
In-Reply-To: <20240130001938.1103354-2-alan.adamson@oracle.com>

> +static ssize_t nvme_adm_passthru_err_log_enabled_show(struct device *dev,
> +		struct device_attribute *attr, char *buf)
> +{
> +	struct nvme_ctrl *ctrl = dev_get_drvdata(dev);
> +
> +	return sysfs_emit(buf, ctrl->passthru_err_log_enabled ? "on" : "off");
> +}
> +

just like in nvme_io_passthru_err_log_enable_show() see below we need "\n"
to be consistent:-

return sysfs_emit(buf, ctrl->passthru_err_log_enabled ? "on\n" : "off\n");

with that Looks good.

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

[...]

> tatic ssize_t nvme_io_passthru_err_log_enabled_show(struct device *dev,
> +		struct device_attribute *attr, char *buf)
> +{
> +	struct nvme_ns *n = dev_get_drvdata(dev);
> +
> +	return sysfs_emit(buf, n->passthru_err_log_enabled ? "on\n" : "off\n");
> +}
> +
>

-ck



  parent reply	other threads:[~2024-01-31 22:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  0:19 [PATCH V9 0/1] nvme: allow passthru cmd error logging Alan Adamson
2024-01-30  0:19 ` [PATCH V9 1/1] " Alan Adamson
2024-01-31  6:23   ` Christoph Hellwig
2024-01-31 22:54   ` Chaitanya Kulkarni [this message]
2024-02-01  1:09   ` Keith Busch

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=efc53006-6174-484b-8560-fac7b3ad3448@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=alan.adamson@oracle.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --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