Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Zhengbin (OSKernel)" <zhengbin13@huawei.com>
To: <hch@infradead.org>, <axboe@kernel.dk>, <bvanassche@acm.org>,
<jaegeuk@kernel.org>, <viro@zeniv.linux.org.uk>,
<linux-fsdevel@vger.kernel.org>, <linux-block@vger.kernel.org>
Cc: <houtao1@huawei.com>, <yi.zhang@huawei.com>
Subject: Re: [PATCH v2 0/2] loop: replace kill_bdev with invalidate_bdev
Date: Thu, 18 Jun 2020 09:11:17 +0800 [thread overview]
Message-ID: <99403447-5460-c143-fd87-425b54d409ef@huawei.com> (raw)
In-Reply-To: <0857bafa-f7ba-dea9-3d5c-7889646b5a37@huawei.com>
ping
On 2020/6/8 10:39, Zhengbin (OSKernel) wrote:
> ping
>
> On 2020/5/30 19:40, Zheng Bin wrote:
>> v1->v2: modify comment, and make function 'kill_bdev' static
>>
>> Zheng Bin (2):
>> loop: replace kill_bdev with invalidate_bdev
>> block: make function 'kill_bdev' static
>>
>> drivers/block/loop.c | 8 ++++----
>> fs/block_dev.c | 5 ++---
>> include/linux/fs.h | 2 --
>> 3 files changed, 6 insertions(+), 9 deletions(-)
>>
>> --
>> 2.21.3
>>
>>
>> .
>>
next prev parent reply other threads:[~2020-06-18 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 11:40 [PATCH v2 0/2] loop: replace kill_bdev with invalidate_bdev Zheng Bin
2020-05-30 11:40 ` [PATCH v2 1/2] " Zheng Bin
2020-06-18 2:14 ` Bart Van Assche
2020-05-30 11:40 ` [PATCH v2 2/2] block: make function 'kill_bdev' static Zheng Bin
2020-05-30 11:36 ` Christoph Hellwig
2020-06-18 2:13 ` Bart Van Assche
2020-06-08 2:39 ` [PATCH v2 0/2] loop: replace kill_bdev with invalidate_bdev Zhengbin (OSKernel)
2020-06-18 1:11 ` Zhengbin (OSKernel) [this message]
2020-06-18 3:46 ` 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=99403447-5460-c143-fd87-425b54d409ef@huawei.com \
--to=zhengbin13@huawei.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=houtao1@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yi.zhang@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).