Re: [PATCH v6 02/18] nvmet/debugfs: Export controller CIU and CIRN via debugfs

Next message: Vidhu Sarwal via B4 Relay: "[PATCH v2 0/3] iio: proximity: Add Benewake TF-Luna LiDAR driver"
Previous message: Jim Mattson: "Re: [PATCH v2 0/2] KVM: nVMX: Don't let L2's LMSW modify CR0 bits owned by L1"
In reply to: Daniel Wagner: "Re: [PATCH v6 02/18] nvmet/debugfs: Export controller CIU and CIRN via debugfs"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: Mohamed Khalfella

Date: Fri Oct 30 2026 - 14:53:18 EST

On Fri 2026-10-30 11:30:00 +0100, Daniel Wagner wrote:
> On Wed, Oct 21, 2026 at 11:38:59AM -0700, Mohamed Khalfella wrote:
> > Good to know that nvme-cli now parses these fields. That is said, the
> > sysfs and debugfs attributes are useful to have. Say the controller is
> > stuck in a state that it can not process an identify command.
>
> Fair enough. I didn't consider this, in this case having the values can
> be helpful. Please add this info to the commit message.

Added a paragraph to the commit message documenting that.