From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
herbert@gondor.apana.org.au
Subject: Re: [PATCH 0/2] Remove custom crc32c init code from btrfs
Date: Mon, 5 Feb 2018 23:59:18 +0100 [thread overview]
Message-ID: <20180205225918.GL18553@twin.jikos.cz> (raw)
In-Reply-To: <1515404705-490-1-git-send-email-nborisov@suse.com>
On Mon, Jan 08, 2018 at 11:45:03AM +0200, Nikolay Borisov wrote:
> So here is a small 2 patch set which removes btrfs' manual initialisation of
> the lower level crc32c module. Explanation why is ok can be found in Patch 2/2.
>
> Patch 1/2 just adds a function to the generic crc32c header which allows
> querying the actual crc32c implementaiton used (i.e. software or hw-accelerated)
> to retain current btrfs behavior. This is mainly used for debugging purposes
> and is independent.
>
> Nikolay Borisov (2):
> libcrc32c: Add crc32c_impl function
> btrfs: Remove custom crc32c init code
As we got ack from Herbert, I'm going to add the patches to my for-next.
prev parent reply other threads:[~2018-02-05 23:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 9:45 Nikolay Borisov
2018-01-08 9:45 ` [PATCH 1/2] libcrc32c: Add crc32c_impl function Nikolay Borisov
2018-02-02 17:29 ` David Sterba
2018-02-03 9:51 ` Herbert Xu
2018-01-08 9:45 ` [PATCH 2/2] btrfs: Remove custom crc32c init code Nikolay Borisov
2018-02-02 17:17 ` David Sterba
2018-02-02 19:46 ` Andy Shevchenko
2018-02-05 22:53 ` David Sterba
2018-01-08 10:21 ` [PATCH 0/2] Remove custom crc32c init code from btrfs Timofey Titovets
2018-01-08 12:30 ` Nikolay Borisov
2018-02-05 22:59 ` David Sterba [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=20180205225918.GL18553@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=herbert@gondor.apana.org.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@suse.com \
/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
all inboxes | Powered by JetHome®