From: Bart Van Assche <bvanassche@acm.org>
To: John Garry <john.g.garry@oracle.com>,
martin.petersen@oracle.com,
james.bottomley@hansenpartnership.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: scsi_debug: Fix atomic write enable module param description
Date: Thu, 11 Dec 2025 11:04:49 -0800 [thread overview]
Message-ID: <760367f9-1cd4-4059-bbdd-9017823e8751@acm.org> (raw)
In-Reply-To: <20251211100651.9056-1-john.g.garry@oracle.com>
On 12/11/25 2:06 AM, John Garry wrote:
> The atomic write enable module param is "atomic_wr", and not
> "atomic_write", so fix the module param description.
>
> Fixes: 84f3a3c01d70 ("scsi: scsi_debug: Atomic write support")
> Signed-off-by: John Garry <john.g.garry@oracle.com>
>
> diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
> index b2ab97be5db3d..047d56d23beab 100644
> --- a/drivers/scsi/scsi_debug.c
> +++ b/drivers/scsi/scsi_debug.c
> @@ -7410,7 +7410,7 @@ MODULE_PARM_DESC(lbprz,
> MODULE_PARM_DESC(lbpu, "enable LBP, support UNMAP command (def=0)");
> MODULE_PARM_DESC(lbpws, "enable LBP, support WRITE SAME(16) with UNMAP bit (def=0)");
> MODULE_PARM_DESC(lbpws10, "enable LBP, support WRITE SAME(10) with UNMAP bit (def=0)");
> -MODULE_PARM_DESC(atomic_write, "enable ATOMIC WRITE support, support WRITE ATOMIC(16) (def=0)");
> +MODULE_PARM_DESC(atomic_wr, "enable ATOMIC WRITE support, support WRITE ATOMIC(16) (def=0)");
> MODULE_PARM_DESC(lowest_aligned, "lowest aligned lba (def=0)");
> MODULE_PARM_DESC(lun_format, "LUN format: 0->peripheral (def); 1 --> flat address method");
> MODULE_PARM_DESC(max_luns, "number of LUNs per target to simulate(def=1)");
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2025-12-11 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 10:06 [PATCH] scsi: scsi_debug: Fix atomic write enable module param description John Garry
2025-12-11 19:04 ` Bart Van Assche [this message]
2025-12-17 3:40 ` Martin K. Petersen
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=760367f9-1cd4-4059-bbdd-9017823e8751@acm.org \
--to=bvanassche@acm.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=john.g.garry@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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