From: Jens Axboe <axboe@kernel.dk>
To: Coly Li <colyli@suse.de>
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 0/7] bcache patches for Linux 5.13 -- 1st wave
Date: Sun, 11 Apr 2021 08:40:07 -0600 [thread overview]
Message-ID: <6808c615-b25c-6ccc-1291-752b42917a2a@kernel.dk> (raw)
In-Reply-To: <20210411134316.80274-1-colyli@suse.de>
On 4/11/21 7:43 AM, Coly Li wrote:
> Hi Jens,
>
> This is the 1st wave of bcache for Linux v5.13.
> All the patches in this submission are all about code cleanup or
> minor fixes.
>
> The 2nd wave patches are about the NVDIMM support on bcache which were
> held in previous merge window. The refined patches work as expected, and
> I am waiting Intel developers to post the update version with the fixes
> of the integration testing. Then I will post out the 2nd wave bcache
> patches for 5.13 merge window.
>
> Thanks in advance for taking the 1st wave patches.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-04-11 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 13:43 [PATCH 0/7] bcache patches for Linux 5.13 -- 1st wave Coly Li
2021-04-11 13:43 ` [PATCH 1/7] bcache: reduce redundant code in bch_cached_dev_run() Coly Li
2021-04-11 13:43 ` [PATCH 2/7] bcache: remove PTR_CACHE Coly Li
2021-04-11 13:43 ` [PATCH 3/7] bcache: use NULL instead of using plain integer as pointer Coly Li
2021-04-11 13:43 ` [PATCH 4/7] md: bcache: avoid -Wempty-body warnings Coly Li
2021-04-11 13:43 ` [PATCH 5/7] md: bcache: Trivial typo fixes in the file journal.c Coly Li
2021-04-11 13:43 ` [PATCH 6/7] bcache: Use 64-bit arithmetic instead of 32-bit Coly Li
2021-04-11 13:43 ` [PATCH 7/7] bcache: fix a regression of code compiling failure in debug.c Coly Li
2021-04-12 9:06 ` Christoph Hellwig
2021-04-12 9:53 ` Coly Li
2021-04-12 12:50 ` Jens Axboe
2021-04-12 13:13 ` Coly Li
2021-04-11 14:40 ` Jens Axboe [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=6808c615-b25c-6ccc-1291-752b42917a2a@kernel.dk \
--to=axboe@kernel.dk \
--cc=colyli@suse.de \
--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