linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ziyang Zhang <ZiyangZhang@linux.alibaba.com>
To: axboe@kernel.dk
Cc: linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] Documentation: document ublk user recovery
Date: Tue, 18 Oct 2022 12:59:09 +0800	[thread overview]
Message-ID: <bef81cd9-86a4-a671-2821-0d7021e4d49a@linux.alibaba.com> (raw)
In-Reply-To: <20221018045346.99706-1-ZiyangZhang@linux.alibaba.com>

Hi Jens,

This doc patch is resent since user recovery feature of ublk has been merged. 
Please consider it.

Regards,
Zhang.

  parent reply	other threads:[~2022-10-18  5:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  4:53 [PATCH 0/1] Documentation: document ublk user recovery ZiyangZhang
2022-10-18  4:53 ` [PATCH 1/1] Documentation: document ublk user recovery feature ZiyangZhang
2022-10-18  4:59 ` Ziyang Zhang [this message]
2022-10-18 12:12 ` [PATCH 0/1] Documentation: document ublk user recovery 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=bef81cd9-86a4-a671-2821-0d7021e4d49a@linux.alibaba.com \
    --to=ziyangzhang@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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).