From: Anand Jain <anand.jain@oracle.com>
To: Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 06/11] btrfs: include linux/crc32c in dir-item and inode-item
Date: Wed, 23 Aug 2023 22:43:31 +0800 [thread overview]
Message-ID: <aa3ca89a-9d02-8aea-daec-f5078a332789@oracle.com> (raw)
In-Reply-To: <6dbf325458ee1c2fc45a66779fd5a277d4f39810.1692798556.git.josef@toxicpanda.com>
On 8/23/23 21:51, Josef Bacik wrote:
> Now these are holding the crc32c wrappers, add the required include so
> that we have our necessary dependencies.
>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> ---
> fs/btrfs/dir-item.h | 2 ++
> fs/btrfs/inode-item.h | 1 +
> 2 files changed, 3 insertions(+)
>
> diff --git a/fs/btrfs/dir-item.h b/fs/btrfs/dir-item.h
> index 951b4dda46fe..5db2ea0dfd76 100644
> --- a/fs/btrfs/dir-item.h
> +++ b/fs/btrfs/dir-item.h
> @@ -3,6 +3,8 @@
> #ifndef BTRFS_DIR_ITEM_H
> #define BTRFS_DIR_ITEM_H
>
> +#include <linux/crc32c.h>
> +
> int btrfs_check_dir_item_collision(struct btrfs_root *root, u64 dir,
> const struct fscrypt_str *name);
> int btrfs_insert_dir_item(struct btrfs_trans_handle *trans,
This could be merged into Patch 4/11.
> diff --git a/fs/btrfs/inode-item.h b/fs/btrfs/inode-item.h
> index 2ee425a08e63..63dfd227e7ce 100644
> --- a/fs/btrfs/inode-item.h
> +++ b/fs/btrfs/inode-item.h
> @@ -4,6 +4,7 @@
> #define BTRFS_INODE_ITEM_H
>
> #include <linux/types.h>
> +#include <linux/crc32c.h>
>
> struct btrfs_trans_handle;
> struct btrfs_root;
And, this can be merged into Patch 3/11.
Otherwise, changes looks fine.
Reviewed-by: Anand Jain <anand.jain@oracle.com>
next prev parent reply other threads:[~2023-08-23 14:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 13:51 [PATCH 00/11] btrfs: ctree.[ch] cleanups Josef Bacik
2023-08-23 13:51 ` [PATCH 01/11] btrfs: move btrfs_crc32c_final into free-space-cache.c Josef Bacik
2023-08-23 14:25 ` Anand Jain
2023-08-28 10:56 ` Johannes Thumshirn
2023-08-23 13:51 ` [PATCH 02/11] btrfs: remove btrfs_crc32c wrapper Josef Bacik
2023-08-23 14:26 ` Anand Jain
2023-08-28 10:58 ` Johannes Thumshirn
2023-08-23 13:51 ` [PATCH 03/11] btrfs: move btrfs_extref_hash into inode-item.h Josef Bacik
2023-08-23 14:29 ` Anand Jain
2023-08-28 10:59 ` Johannes Thumshirn
2023-08-23 13:51 ` [PATCH 04/11] btrfs: move btrfs_name_hash to dir-item.h Josef Bacik
2023-08-23 14:34 ` Anand Jain
2023-08-28 11:00 ` Johannes Thumshirn
2023-08-23 13:51 ` [PATCH 05/11] btrfs: include asm/unaligned.h in accessors.h Josef Bacik
2023-08-28 11:04 ` Johannes Thumshirn
2023-08-23 13:51 ` [PATCH 06/11] btrfs: include linux/crc32c in dir-item and inode-item Josef Bacik
2023-08-23 14:43 ` Anand Jain [this message]
2023-08-23 13:51 ` [PATCH 07/11] btrfs: include linux/iomap.h in file.c Josef Bacik
2023-08-28 11:05 ` Johannes Thumshirn
2023-08-23 13:51 ` [PATCH 08/11] btrfs: add fscrypt related dependencies to respective headers Josef Bacik
2023-08-28 11:06 ` Johannes Thumshirn
2023-08-23 13:51 ` [PATCH 09/11] btrfs: add btrfs_delayed_ref_head declaration to extent-tree.h Josef Bacik
2023-08-28 11:06 ` Johannes Thumshirn
2023-08-23 13:51 ` [PATCH 10/11] btrfs: include trace header in where necessary Josef Bacik
2023-08-28 11:07 ` Johannes Thumshirn
2023-08-23 13:51 ` [PATCH 11/11] btrfs: remove extraneous includes from ctree.h Josef Bacik
2023-08-25 14:21 ` kernel test robot
2023-08-28 11:08 ` Johannes Thumshirn
2023-08-28 13:29 ` Josef Bacik
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=aa3ca89a-9d02-8aea-daec-f5078a332789@oracle.com \
--to=anand.jain@oracle.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).