From: Christoph Hellwig <hch@lst.de>
To: Mike Christie <michael.christie@oracle.com>
Cc: john.g.garry@oracle.com, bvanassche@acm.org, mwilck@suse.com,
hch@lst.de, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org,
james.bottomley@hansenpartnership.com
Subject: Re: [PATCH v4 00/15] scsi: Add struct for args to execution functions
Date: Sun, 8 Jan 2023 18:52:48 +0100 [thread overview]
Message-ID: <20230108175248.GA23317@lst.de> (raw)
In-Reply-To: <20221229190154.7467-1-michael.christie@oracle.com>
The whole series looks good to me:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2023-01-08 17:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 19:01 [PATCH v4 00/15] scsi: Add struct for args to execution functions Mike Christie
2022-12-29 19:01 ` [PATCH v4 01/15] " Mike Christie
2022-12-29 19:01 ` [PATCH v4 02/15] ata: libata-scsi: Convert to scsi_execute_cmd Mike Christie
2022-12-29 19:01 ` [PATCH v4 03/15] hwmon: drivetemp: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 04/15] scsi: ch: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 05/15] scsi: scsi_dh: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 06/15] scsi: core: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 07/15] scsi: spi: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 08/15] scsi: sd: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 09/15] scsi: zbc: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 10/15] scsi: ses: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 11/15] scsi: sr: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 12/15] scsi: virtio_scsi: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 13/15] scsi: target_core_pscsi: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 14/15] scsi: cxlflash: " Mike Christie
2022-12-29 19:01 ` [PATCH v4 15/15] scsi: Remove scsi_execute_req/scsi_execute functions Mike Christie
2023-01-08 17:52 ` Christoph Hellwig [this message]
2023-01-14 2:41 ` [PATCH v4 00/15] scsi: Add struct for args to execution functions 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=20230108175248.GA23317@lst.de \
--to=hch@lst.de \
--cc=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 \
--cc=michael.christie@oracle.com \
--cc=mwilck@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.