From: Keith Busch <kbusch@kernel.org>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: mlombard@bsdbackstore.eu, bgurney@redhat.com, bvanassche@acm.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH V2] nvme: expose active quirks in sysfs
Date: Tue, 13 Jan 2026 14:53:31 -0700 [thread overview]
Message-ID: <aWa-209BvYmbYWJc@kbusch-mbp> (raw)
In-Reply-To: <20251103144406.1148401-1-mlombard@redhat.com>
On Mon, Nov 03, 2025 at 03:44:06PM +0100, Maurizio Lombardi wrote:
> Currently, there is no straightforward way for a user to inspect
> which quirks are active for a given device from userspace.
>
> Add a new "quirks" sysfs attribute to the nvme controller device.
>
> Reading this file will display a human-readable list
> of all active quirks, with each quirk name on a new line.
> If no quirks are active, it will display "none".
Thanks, applied to nvme-7.0.
prev parent reply other threads:[~2026-01-13 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 14:44 [PATCH V2] nvme: expose active quirks in sysfs Maurizio Lombardi
2025-11-03 20:29 ` Chaitanya Kulkarni
2025-11-05 3:05 ` Martin K. Petersen
2025-11-17 22:12 ` John Meneghini
2025-11-18 1:46 ` Chaitanya Kulkarni
2025-11-30 23:09 ` Sagi Grimberg
2025-12-09 22:02 ` Maurizio Lombardi
2026-01-13 21:53 ` Keith Busch [this message]
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=aWa-209BvYmbYWJc@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=bgurney@redhat.com \
--cc=bvanassche@acm.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@bsdbackstore.eu \
--cc=mlombard@redhat.com \
/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