From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Garry <john.g.garry@oracle.com>
Cc: martin.petersen@oracle.com, target-devel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
michael.christie@oracle.com
Subject: Re: [PATCH v3 0/7] scsi: target: Add WRITE_ATOMIC_16 support
Date: Sun, 02 Nov 2025 21:43:12 -0500 [thread overview]
Message-ID: <yq1wm47suoc.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20251020103820.2917593-1-john.g.garry@oracle.com> (John Garry's message of "Mon, 20 Oct 2025 10:38:13 +0000")
John,
> This is a reposting of Mike's atomic writes support for the SCSI
> target.
>
> Again, we are now only supporting target_core_iblock. It's implemented
> similar to UNMAP where we do not do any emulation and instead pass the
> operation to the block layer.
Applied to 6.19/scsi-staging, thanks!
--
Martin K. Petersen
next prev parent reply other threads:[~2025-11-03 2:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 10:38 [PATCH v3 0/7] scsi: target: Add WRITE_ATOMIC_16 support John Garry
2025-10-20 10:38 ` [PATCH v3 1/7] scsi: target: Rename target_configure_unmap_from_queue John Garry
2025-10-20 10:38 ` [PATCH v3 2/7] scsi: target: Add atomic se_device fields John Garry
2025-10-20 10:38 ` [PATCH v3 3/7] scsi: target: Add helper to setup atomic values from block_device John Garry
2025-10-20 10:38 ` [PATCH v3 4/7] scsi: target: Add WRITE_ATOMIC_16 handler John Garry
2025-10-20 10:38 ` [PATCH v3 5/7] scsi: target: Report atomic values in INQUIRY John Garry
2025-10-20 10:38 ` [PATCH v3 6/7] scsi: target: Add WRITE_ATOMIC_16 support to RSOC John Garry
2025-10-20 10:38 ` [PATCH v3 7/7] scsi: target: Add atomic support to target_core_iblock John Garry
2025-11-03 2:43 ` Martin K. Petersen [this message]
2025-11-05 4:02 ` [PATCH v3 0/7] scsi: target: Add WRITE_ATOMIC_16 support 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=yq1wm47suoc.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=target-devel@vger.kernel.org \
/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