From: Jens Axboe <axboe@kernel.dk>
To: Ritika Srivastava <RITIKA.SRIVASTAVA@ORACLE.COM>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 1/2] block: Return blk_status_t instead of errno codes
Date: Wed, 26 Aug 2020 11:19:56 -0600 [thread overview]
Message-ID: <de5c94ec-9079-22b7-bbcd-667f3b0fe94e@kernel.dk> (raw)
In-Reply-To: <C6F86C38-BE29-422A-8A57-5144E26C4569@ORACLE.COM>
On 8/26/20 11:03 AM, Ritika Srivastava wrote:
> Hi Jens,
>
> Can the following patches please be applied.
>
> [PATCH 1/2] block: Return blk_status_t instead of errno codes
> [PATCH v4 2/2] block: better deal with the delayed not supported case in blk_cloned_rq_check_limits
Can you resend them against the current tree? They don't apply.
--
Jens Axboe
next prev parent reply other threads:[~2020-08-26 17:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 22:47 Return BLK_STS_NOTSUPP and blk_status_t from blk_cloned_rq_check_limits() Ritika Srivastava
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 [this message]
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 20:17 ` [PATCH 1/2] block: Return blk_status_t instead of errno codes Ritika Srivastava
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=de5c94ec-9079-22b7-bbcd-667f3b0fe94e@kernel.dk \
--to=axboe@kernel.dk \
--cc=RITIKA.SRIVASTAVA@ORACLE.COM \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).