From: Coly Li <colyli@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: kent.overstreet@gmail.com, liangchen.linux@gmail.com,
linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: bcache kbuild cleanups
Date: Mon, 9 Dec 2019 17:59:13 +0800 [thread overview]
Message-ID: <b19f677f-d8e5-44af-0575-d1fb74835c65@suse.de> (raw)
In-Reply-To: <20191209093829.19703-1-hch@lst.de>
On 2019/12/9 5:38 下午, Christoph Hellwig wrote:
> Hi Coly and Liang,
>
> can you review this series to sort out the bcache superblock reading for
> larger page sizes? I don't have bcache test setup so this is compile
> tested only.
>
Hi Christoph,
At first glance the patches are good. I will add them into my for-test
directory and test with other development patches.
Thanks for handling this.
--
Coly Li
next prev parent reply other threads:[~2019-12-09 9:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 9:38 bcache kbuild cleanups Christoph Hellwig
2019-12-09 9:38 ` [PATCH 1/7] bcache: cached_dev_free needs to put the sb page Christoph Hellwig
2019-12-09 9:38 ` [PATCH 2/7] bcache: use a separate data structure for the on-disk super block Christoph Hellwig
2019-12-09 9:38 ` [PATCH 3/7] bcache: rework error unwinding in register_bcache Christoph Hellwig
2019-12-09 9:38 ` [PATCH 4/7] bcache: transfer the sb_page reference to register_{bdev,cache} Christoph Hellwig
2019-12-09 9:38 ` [PATCH 5/7] bcache: return a pointer to the on-disk sb from read_super Christoph Hellwig
2019-12-09 9:38 ` [PATCH 6/7] bcache: store a pointer to the on-disk sb in the cache and cached_dev structures Christoph Hellwig
2019-12-09 9:38 ` [PATCH 7/7] bcache: use read_cache_page_gfp to read the superblock Christoph Hellwig
2019-12-09 9:59 ` Coly Li [this message]
2019-12-11 15:17 ` bcache kbuild cleanups Liang C
2019-12-12 15:34 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-10-15 16:04 Christoph Hellwig
2019-10-20 6:24 ` Coly Li
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=b19f677f-d8e5-44af-0575-d1fb74835c65@suse.de \
--to=colyli@suse.de \
--cc=hch@lst.de \
--cc=kent.overstreet@gmail.com \
--cc=liangchen.linux@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@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 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.