From: Ziyang Zhang <ZiyangZhang@linux.alibaba.com>
To: Jens Axboe <axboe@kernel.dk>, ming.lei@redhat.com
Cc: xiaoguang.wang@linux.alibaba.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, joseph.qi@linux.alibaba.com
Subject: Re: [PATCH V6 0/7] ublk_drv: add USER_RECOVERY support
Date: Mon, 26 Sep 2022 09:36:12 +0800 [thread overview]
Message-ID: <45b4b583-d108-b8a2-eee3-3bce755f31ed@linux.alibaba.com> (raw)
In-Reply-To: <88fb97a1-23a1-9f75-a9fa-54b233e0a39e@kernel.dk>
On 2022/9/24 09:12, Jens Axboe wrote:
>
> I'm going to apply 1-6 for 6.1, applying the doc patch is difficult as
> it only went into 6.0 past forking off the 6.1 block branch. Would you
> mind resending the 7/7 patch once the merge window opens and I've pushed
> the previous bits? I may forget otherwise...
OK, I will resend the doc patch.
Regards,
Zhang
prev parent reply other threads:[~2022-09-26 1:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 15:39 [PATCH V6 0/7] ublk_drv: add USER_RECOVERY support ZiyangZhang
2022-09-23 15:39 ` [PATCH V6 1/7] ublk_drv: check 'current' instead of 'ubq_daemon' ZiyangZhang
2022-09-23 15:39 ` [PATCH V6 2/7] ublk_drv: define macros for recovery feature and check them ZiyangZhang
2022-09-23 15:39 ` [PATCH V6 3/7] ublk_drv: requeue rqs with recovery feature enabled ZiyangZhang
2022-09-23 15:39 ` [PATCH V6 4/7] ublk_drv: consider recovery feature in aborting mechanism ZiyangZhang
2022-09-23 15:39 ` [PATCH V6 5/7] ublk_drv: support UBLK_F_USER_RECOVERY_REISSUE ZiyangZhang
2022-09-23 15:39 ` [PATCH V6 6/7] ublk_drv: add START_USER_RECOVERY and END_USER_RECOVERY support ZiyangZhang
2022-09-23 15:39 ` [PATCH V6 7/7] Documentation: document ublk user recovery feature ZiyangZhang
2022-09-24 1:02 ` Ming Lei
2022-09-24 1:12 ` [PATCH V6 0/7] ublk_drv: add USER_RECOVERY support Jens Axboe
2022-09-26 1:36 ` Ziyang Zhang [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=45b4b583-d108-b8a2-eee3-3bce755f31ed@linux.alibaba.com \
--to=ziyangzhang@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=xiaoguang.wang@linux.alibaba.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