From: Coly Li <colyli@suse.de>
To: axboe@kernel.dk
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
Coly Li <colyli@suse.de>
Subject: [PATCH 0/8] bcache patches for Linux v5.16 (first wave)
Date: Wed, 20 Oct 2021 22:28:49 +0800 [thread overview]
Message-ID: <20211020142857.6320-1-colyli@suse.de> (raw)
Hi Jens,
This is the first wave bcache series for Linux v5.16. In this merge
window, there is no large change set submitted, most of the patches
are code clean up from Chao, Christoph and me. This time we have a
new contributor Feng who provides a useful bug fix for dirty data size
calculation during cache detaching.
Please take them and thanks in advance.
Coly Li
---
Chao Yu (1):
bcache: fix error info in register_bcache()
Christoph Hellwig (4):
bcache: remove the cache_dev_name field from struct cache
bcache: remove the backing_dev_name field from struct cached_dev
bcache: use bvec_kmap_local in bch_data_verify
bcache: remove bch_crc64_update
Coly Li (1):
bcache: reserve never used bits from bkey.high
Ding Senjie (1):
md: bcache: Fix spelling of 'acquire'
Lin Feng (1):
bcache: move calc_cached_dev_sectors to proper place on backing device
detach
drivers/md/bcache/bcache.h | 4 ---
drivers/md/bcache/btree.c | 2 +-
drivers/md/bcache/debug.c | 15 ++++----
drivers/md/bcache/io.c | 16 ++++-----
drivers/md/bcache/request.c | 6 ++--
drivers/md/bcache/super.c | 72 ++++++++++++++++++-------------------
drivers/md/bcache/sysfs.c | 2 +-
drivers/md/bcache/util.h | 8 -----
include/uapi/linux/bcache.h | 4 +--
9 files changed, 57 insertions(+), 72 deletions(-)
--
2.31.1
next reply other threads:[~2021-10-20 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 14:28 Coly Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-20 14:38 [PATCH 0/8] bcache patches for Linux v5.16 (first wave) Coly Li
2021-10-20 14:41 ` 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=20211020142857.6320-1-colyli@suse.de \
--to=colyli@suse.de \
--cc=axboe@kernel.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox