From: Mike Christie <mchristi@redhat.com>
To: axboe@kernel.dk, josef@toxicpanda.com, linux-block@vger.kernel.org
Subject: [PATCH 0/4] nbd: cmd timeout fixes V2
Date: Tue, 13 Aug 2019 11:39:48 -0500 [thread overview]
Message-ID: <20190813163952.23486-1-mchristi@redhat.com> (raw)
The following patches fix bugs related to the nbd cmd timeout feature.
The patches were made over Linus's current tree and also apply over
this nbd patch:
https://marc.info/?l=linux-block&m=156494582914495&w=2
V2:
- Fix patch4 so it allows resetting of the nbd cmd timeout to 0 as well
initializing it to 0.
- Add Josef's revewied-by tag.
next reply other threads:[~2019-08-13 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 16:39 Mike Christie [this message]
2019-08-13 16:39 ` [PATCH 1/4] nbd: add set cmd timeout helper Mike Christie
2019-08-13 16:39 ` [PATCH 2/4] nbd: add function to convert blk req op to nbd cmd Mike Christie
2019-08-13 16:39 ` [PATCH 3/4] nbd: add missing config put Mike Christie
2019-08-13 16:39 ` [PATCH 4/4] nbd: fix zero cmd timeout handling v2 Mike Christie
2019-08-20 18:44 ` [PATCH 0/4] nbd: cmd timeout fixes V2 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=20190813163952.23486-1-mchristi@redhat.com \
--to=mchristi@redhat.com \
--cc=axboe@kernel.dk \
--cc=josef@toxicpanda.com \
--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).