From: Bob Peterson Date: Thu, 1 Feb 2018 13:59:20 -0500 (EST) Subject: [Cluster-devel] [PATCH] gfs2: Fix the crc32c dependency In-Reply-To: <20180201142835.29053-1-agruenba@redhat.com> References: <20180201142835.29053-1-agruenba@redhat.com> Message-ID: <1607563068.6106789.1517511560621.JavaMail.zimbra@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit ----- Original Message ----- | Depend on LIBCRC32C which uses the crypto API to select the appropriate | crc32c implementation. With the CRYPTO and CRYPTO_CRC32C dependencies, | gfs2 would still need to use the crypto API directly like ext4 and btrfs | do, which isn't necessary. | | Signed-off-by: Andreas Gruenbacher | --- Hi, Thanks. This is now pushed to the for-next branch of the linux-gfs2 tree: https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs?h=for-next&id=dcb2cd55cf43fe06ada66265c1e088a4b08d3e3d Regards, Bob Peterson Red Hat File Systems