From: Markus Elfring <Markus.Elfring@web.de>
To: Aditya Pakki <pakki001@umn.edu>,
ceph-devel@vger.kernel.org, linux-block@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Dongsheng Yang <dongsheng.yang@easystack.cn>,
Ilya Dryomov <idryomov@gmail.com>, Jens Axboe <axboe@kernel.dk>,
Kangjie Lu <kjlu@umn.edu>, Sage Weil <sage@redhat.com>
Subject: Re: [PATCH] rbd: Avoid calling BUG() when object_map is not empty
Date: Sun, 15 Dec 2019 23:00:06 +0100 [thread overview]
Message-ID: <2b5305f3-1224-01a4-ee52-5e05b92e56d6@web.de> (raw)
In-Reply-To: <20191215163527.25203-1-pakki001@umn.edu>
> The patch fixes this issue.
Will the tag “Fixes” be more helpful than this sentence?
Regards,
Markus
next prev parent reply other threads:[~2019-12-15 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 16:35 [PATCH] rbd: Avoid calling BUG() when object_map is not empty Aditya Pakki
2019-12-15 22:00 ` Markus Elfring [this message]
2019-12-16 10:18 ` Ilya Dryomov
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=2b5305f3-1224-01a4-ee52-5e05b92e56d6@web.de \
--to=markus.elfring@web.de \
--cc=axboe@kernel.dk \
--cc=ceph-devel@vger.kernel.org \
--cc=dongsheng.yang@easystack.cn \
--cc=idryomov@gmail.com \
--cc=kjlu@umn.edu \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pakki001@umn.edu \
--cc=sage@redhat.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;
as well as URLs for NNTP newsgroup(s).