From: Kashyap Desai <kashyap.desai@broadcom.com>
To: dgilbert@interlog.com
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
Hannes Reinecke <hare@suse.de>
Subject: RE: [PATCH v3] scsi_debug: add new defer_type for mq_poll
Date: Fri, 12 Feb 2021 16:41:40 +0530 [thread overview]
Message-ID: <5f24045907d63e5226c99e1f5942729a@mail.gmail.com> (raw)
In-Reply-To: <9fc5ef5c-1871-c0e1-8ba6-1489c4a0656a@interlog.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
> > So how shall we progress now ? Shall I ask Martin to pick all the
> > patches from " [PATCH v3 0/4] io_uring iopoll in scsi layer" since
> > this patch has dependency on my series.
>
> Kashyap,
> Good catch!
>
> You could roll all the scsi_debug stuff into one patch and put both our
> sign-
> offs on it, or present it as two patches:
> - first one: your original plus this fix
> - second one: mine with your tested-by on it
Doug - I will include your patch "scsi_debug: add new defer_type for
mq_poll" (including the recent fix) as separate patch in my series and
provide Tested-by tag for the same.
>
> Since this is new functionality for the scsi sub-system, it is unlikely
> that all the
> corner cases have been visited. However, with what we have in place for
> the
> next cycle, others have something reasonably solid to build on.
Agree.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4169 bytes --]
prev parent reply other threads:[~2021-02-12 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 22:56 [PATCH v3] scsi_debug: add new defer_type for mq_poll Douglas Gilbert
2021-02-10 3:08 ` Kashyap Desai
2021-02-10 17:31 ` Douglas Gilbert
2021-02-11 5:56 ` Douglas Gilbert
2021-02-11 12:13 ` Kashyap Desai
2021-02-11 16:11 ` Douglas Gilbert
2021-02-12 11:11 ` Kashyap Desai [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=5f24045907d63e5226c99e1f5942729a@mail.gmail.com \
--to=kashyap.desai@broadcom.com \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.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