Linux bcache driver list
 help / color / mirror / Atom feed
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/2] bcache paches for Linux v5.16 (2nd wave)
Date: Fri, 29 Oct 2021 06:43:38 -0600	[thread overview]
Message-ID: <163551141854.81306.9109988808769746352.b4-ty@kernel.dk> (raw)
In-Reply-To: <20211029060930.119923-1-colyli@suse.de>

On Fri, 29 Oct 2021 14:09:28 +0800, Coly Li wrote:
> This is the second wave of bcache patches for Linux v5.16.
> 
> The first patch is suggested by Arnd Bergmann and Christoph
> Hellwig that the bcache.h should not belong to include/uapi/
> directory, and I compose the change.
> 
> The second patch is code cleanup to remove coccicheck warning
> which suggests to use scnprintf to replace snprintf(), Qing
> Wang posts the change to remove the warning by using sysfs_emit().
> 
> [...]

Applied, thanks!

[1/2] bcache: move uapi header bcache.h to bcache code directory
      commit: cf2197ca4b8c199d188593ca6800ea1827c42171
[2/2] bcache: replace snprintf in show functions with sysfs_emit
      commit: 1b86db5f4e025840e0bf7cef2b10e84531954386

Best regards,
-- 
Jens Axboe



  parent reply	other threads:[~2021-10-29 12:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29  6:09 [PATCH 0/2] bcache paches for Linux v5.16 (2nd wave) Coly Li
2021-10-29  6:09 ` [PATCH 1/2] bcache: move uapi header bcache.h to bcache code directory Coly Li
2021-10-29  6:09 ` [PATCH 2/2] bcache: replace snprintf in show functions with sysfs_emit Coly Li
2021-10-29 12:43 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-29  6:08 [PATCH 0/2] bcache paches for Linux v5.16 (2nd wave) 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=163551141854.81306.9109988808769746352.b4-ty@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