All of lore.kernel.org
 help / color / mirror / Atom feed
From: Coly Li <colyli@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 00/12] bcache patches for Linux v4.21
Date: Fri, 14 Dec 2018 16:25:16 +0800	[thread overview]
Message-ID: <a1b4c966-b3ba-8a72-2e7b-4890ee1d41e3@suse.de> (raw)
In-Reply-To: <2443d456-f537-ef08-f550-3e4ac2a116af@kernel.dk>

On 12/13/18 11:16 PM, Jens Axboe wrote:
> On 12/13/18 7:53 AM, Coly Li wrote:
>> Hi Jens,
>>
>> Here are the patches for Linux v4.21.
>>
>> The patches from me are for a set of disabled-by-default optimization
>> for writeback cache mode, which are used by some users I know. Guoju
>> Fang contributes a patch to add number of keys in
>> trace_bcache_journal_write(). And there are 6 patchges are from Shenghui
>> Wang, which removes an unncessary NULL check for
>> debugfs_remove_recursive() and debugfs_remove(), adds useful code
>> comments for bcache, and improves sysfs information display for bcache
>> writeback rate parameters.
>>
>> We don't have important or big change in this run. Please take these
>> patches.
> 
> Applied, thanks.
> 
> Note that I reformated some of the commit messages and patch headers.
> Keep them within 72 chars, then everything is much more readable
> in git log.

Hi Jens,

Sure I will take more attention on the 72 chars limit, thanks for your
remind.

Coly Li

      reply	other threads:[~2018-12-14  8:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 14:53 [PATCH 00/12] bcache patches for Linux v4.21 Coly Li
2018-12-13 14:53 ` [PATCH 01/12] bcache: add comment for cache_set->fill_iter Coly Li
2018-12-13 14:53 ` [PATCH 02/12] bcache: do not check if debug dentry is ERR or NULL explicitly on remove Coly Li
2018-12-13 14:53 ` [PATCH 03/12] bcache: update comment for bch_data_insert Coly Li
2018-12-13 14:53 ` [PATCH 04/12] bcache: update comment in sysfs.c Coly Li
2018-12-13 14:53 ` [PATCH 05/12] bcache: do not mark writeback_running until backing dev attached to cache_set Coly Li
2018-12-13 14:53 ` [PATCH 06/12] bcache: cannot set writeback_running via sysfs if no writeback kthread created Coly Li
2018-12-13 14:53 ` [PATCH 07/12] bcache: introduce force_wake_up_gc() Coly Li
2018-12-13 14:53 ` [PATCH 08/12] bcache: option to automatically run gc thread after writeback accomplished Coly Li
2018-12-13 14:53 ` [PATCH 09/12] bcache: add MODULE_DESCRIPTION information Coly Li
2018-12-13 14:53 ` [PATCH 10/12] bcache: make cutoff_writeback and cutoff_writeback_sync tunnable Coly Li
2018-12-13 14:53 ` [PATCH 11/12] bcache: set writeback_percent in a flexible range Coly Li
2018-12-13 14:53 ` [PATCH 12/12] bcache: print number of keys in trace_bcache_journal_write Coly Li
2018-12-13 15:16 ` [PATCH 00/12] bcache patches for Linux v4.21 Jens Axboe
2018-12-14  8:25   ` Coly Li [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=a1b4c966-b3ba-8a72-2e7b-4890ee1d41e3@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 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.