All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: ZiyangZhang <ZiyangZhang@linux.alibaba.com>
Cc: axboe@kernel.dk, xiaoguang.wang@linux.alibaba.com,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	joseph.qi@linux.alibaba.com
Subject: Re: [PATCH V6 7/7] Documentation: document ublk user recovery feature
Date: Sat, 24 Sep 2022 09:02:28 +0800	[thread overview]
Message-ID: <Yy5XJOuvFH+2dXfP@T590> (raw)
In-Reply-To: <20220923153919.44078-8-ZiyangZhang@linux.alibaba.com>

On Fri, Sep 23, 2022 at 11:39:19PM +0800, ZiyangZhang wrote:
> Add documentation for user recovery feature of ublk subsystem.
> 
> Signed-off-by: ZiyangZhang <ZiyangZhang@linux.alibaba.com>
> ---

Reviewed-by: Ming Lei <ming.lei@redhat.com>


Thanks,
Ming


  reply	other threads:[~2022-09-24  1:02 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 [this message]
2022-09-24  1:12 ` [PATCH V6 0/7] ublk_drv: add USER_RECOVERY support Jens Axboe
2022-09-26  1:36   ` Ziyang Zhang

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=Yy5XJOuvFH+2dXfP@T590 \
    --to=ming.lei@redhat.com \
    --cc=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=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 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.