From: John Garry <john.g.garry@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org,
Douglas Gilbert <dgilbert@interlog.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>
Subject: Re: [PATCH] scsi_debug: Make CRC_T10DIF support optional
Date: Fri, 1 Mar 2024 18:18:01 +0000 [thread overview]
Message-ID: <fcad0227-dfd9-4fe4-b977-2eaf6242ea48@oracle.com> (raw)
In-Reply-To: <61b4391a-8613-4ca5-b250-3253f2085712@acm.org>
On 01/03/2024 16:30, Bart Van Assche wrote:
>>> Not all scsi_debug users need data integrity support. Hence modify the
>>> scsi_debug driver such that it becomes possible to build this driver
>>> without data integrity support.
>>>
>>> Cc: Douglas Gilbert<dgilbert@interlog.com>
>>> Signed-off-by: Bart Van Assche<bvanassche@acm.org>
>>> ---
>>> drivers/scsi/Kconfig | 2 +-
>>> drivers/scsi/Makefile | 2 +
>>> drivers/scsi/scsi_debug-dif.h | 65 +++++
>>> drivers/scsi/scsi_debug_dif.c | 224 +++++++++++++++
>>> .../scsi/{scsi_debug.c => scsi_debug_main.c} | 257 ++----------------
>>> 5 files changed, 308 insertions(+), 242 deletions(-)
>>
>> That's a pretty light commit message for so many modifications.
>
> Hi John,
>
> Thanks for having taken a look. The patch description is short because
> this patch doesn't do much: it
> splits the scsi_debug source code in two
> files and modifies the Kconfig and Makefile. No functional changes are
> present in this patch.
I think that this info is useful.
About this:
On 29/02/2024 17:23, Bart Van Assche wrote:
> config SCSI_DEBUG
> tristate "SCSI debugging host and device simulator"
> depends on SCSI
> - select CRC_T10DIF
> + select CRC_T10DIF if SCSI_DEBUG = y
So this means that we select CRC_T10DIF if SCSI_DEBUG is only built-in,
right?
Thanks,
John
next prev parent reply other threads:[~2024-03-01 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 17:23 [PATCH] scsi_debug: Make CRC_T10DIF support optional Bart Van Assche
2024-03-01 8:59 ` John Garry
2024-03-01 16:30 ` Bart Van Assche
2024-03-01 18:18 ` John Garry [this message]
2024-03-01 23:03 ` Bart Van Assche
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=fcad0227-dfd9-4fe4-b977-2eaf6242ea48@oracle.com \
--to=john.g.garry@oracle.com \
--cc=bvanassche@acm.org \
--cc=dgilbert@interlog.com \
--cc=jejb@linux.ibm.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