From: Ritika Srivastava <ritika.srivastava@oracle.com>
To: linux-block@vger.kernel.org
Cc: axboe@kernel.dk, ritika.srivastava@oracle.com
Subject: Return BLK_STS_NOTSUPP and blk_status_t from blk_cloned_rq_check_limits()
Date: Wed, 29 Jul 2020 15:47:56 -0700 [thread overview]
Message-ID: <1596062878-4238-1-git-send-email-ritika.srivastava@oracle.com> (raw)
Hi,
These patches address the comments from previous v1 version
block: return BLK_STS_NOTSUPP if operation is not supported
Updates since v1:
- Document scenario and SCSI error encountered in a comment in blk_cloned_rq_check_limits().
- Add a patch to switch returning errno codes to blk_status_t in blk_cloned_rq_check_limits().
Please review the following patches.
[PATCH 1/2] block: Return blk_status_t instead of errno codes
[PATCH v2 2/2] block: return BLK_STS_NOTSUPP if operation is not supported
Thanks,
Ritika
next reply other threads:[~2020-07-29 23:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 22:47 Ritika Srivastava [this message]
2020-07-29 22:47 ` [PATCH 1/2] block: Return blk_status_t instead of errno codes Ritika Srivastava
2020-08-14 6:26 ` Christoph Hellwig
2020-08-26 17:03 ` Ritika Srivastava
2020-08-26 17:19 ` Jens Axboe
2020-08-26 17:23 ` Ritika Srivastava
2020-08-28 15:52 ` Ritika Srivastava
2020-08-28 15:52 ` Jens Axboe
2020-08-28 17:10 ` Ritika Srivastava
2020-08-31 15:38 ` Jens Axboe
2020-08-31 23:02 ` Ritika Srivastava
2020-07-29 22:47 ` [PATCH v2 2/2] block: return BLK_STS_NOTSUPP if operation is not supported Ritika Srivastava
2020-08-14 6:37 ` Christoph Hellwig
2020-08-17 18:10 ` Ritika Srivastava
2020-08-05 17:54 ` Return BLK_STS_NOTSUPP and blk_status_t from blk_cloned_rq_check_limits() Ritika Srivastava
2020-08-13 19:13 ` Ritika Srivastava
2020-09-01 20:17 Ritika Srivastava
2020-09-01 22:56 ` Jens Axboe
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=1596062878-4238-1-git-send-email-ritika.srivastava@oracle.com \
--to=ritika.srivastava@oracle.com \
--cc=axboe@kernel.dk \
--cc=linux-block@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 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.