From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Pavel Tatashin <pasha.tatashin@soleen.com>,
"tyhicks@linux.microsoft.com" <tyhicks@linux.microsoft.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sashal@kernel.org" <sashal@kernel.org>,
"jmorris@namei.org" <jmorris@namei.org>,
"lukas.bulwahn@gmail.com" <lukas.bulwahn@gmail.com>,
"hch@lst.de" <hch@lst.de>, "pvorel@suse.cz" <pvorel@suse.cz>,
"ming.lei@redhat.com" <ming.lei@redhat.com>,
"mzxreary@0pointer.de" <mzxreary@0pointer.de>,
"mcgrof@kernel.org" <mcgrof@kernel.org>,
"zhengbin13@huawei.com" <zhengbin13@huawei.com>,
"maco@android.com" <maco@android.com>,
"colin.king@canonical.com" <colin.king@canonical.com>,
"evgreen@chromium.org" <evgreen@chromium.org>
Subject: Re: [PATCH v4 0/1] scale loop device lock
Date: Tue, 26 Jan 2021 19:03:39 +0000 [thread overview]
Message-ID: <BYAPR04MB4965C4E9FB75135F317CF34F86BC9@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20210126144630.230714-1-pasha.tatashin@soleen.com
Pavel,
On 1/26/21 6:48 AM, Pavel Tatashin wrote:
> Changelog
> v4
> - Added review-by Petr Vorel
> - Addressed comments from Chaitanya Kulkarni
Thanks a lot for making these changes, detail commit log helps everyone
in the community and not just to the owner.
prev parent reply other threads:[~2021-01-27 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 14:46 [PATCH v4 0/1] scale loop device lock Pavel Tatashin
2021-01-26 14:46 ` [PATCH v4 1/1] loop: scale loop device by introducing per " Pavel Tatashin
2021-01-26 20:09 ` Jens Axboe
2021-01-27 16:12 ` Pavel Tatashin
2021-01-26 19:03 ` Chaitanya Kulkarni [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=BYAPR04MB4965C4E9FB75135F317CF34F86BC9@BYAPR04MB4965.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=axboe@kernel.dk \
--cc=colin.king@canonical.com \
--cc=evgreen@chromium.org \
--cc=hch@lst.de \
--cc=jmorris@namei.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=maco@android.com \
--cc=mcgrof@kernel.org \
--cc=ming.lei@redhat.com \
--cc=mzxreary@0pointer.de \
--cc=pasha.tatashin@soleen.com \
--cc=pvorel@suse.cz \
--cc=sashal@kernel.org \
--cc=tyhicks@linux.microsoft.com \
--cc=zhengbin13@huawei.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).