linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH v2 12/12] btrfs: remove extraneous includes from ctree.h
Date: Fri, 25 Aug 2023 16:19:30 -0400	[thread overview]
Message-ID: <15d63abd06cb64b7edc83d033e65ca00a2bae3ba.1692994620.git.josef@toxicpanda.com> (raw)
In-Reply-To: <cover.1692994620.git.josef@toxicpanda.com>

We don't need any of these includes in the ctree.h header file for the
header file itself, remove them to clean up ctree.h a little bit.

Signed-off-by: Josef Bacik <josef@toxicpanda.com>
---
 fs/btrfs/ctree.h | 28 ----------------------------
 1 file changed, 28 deletions(-)

diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index 9c2e96b8711f..da9e07bf76ea 100644
--- a/fs/btrfs/ctree.h
+++ b/fs/btrfs/ctree.h
@@ -6,36 +6,8 @@
 #ifndef BTRFS_CTREE_H
 #define BTRFS_CTREE_H
 
-#include <linux/mm.h>
-#include <linux/sched/signal.h>
-#include <linux/highmem.h>
-#include <linux/fs.h>
-#include <linux/rwsem.h>
-#include <linux/semaphore.h>
-#include <linux/completion.h>
-#include <linux/backing-dev.h>
-#include <linux/wait.h>
-#include <linux/slab.h>
-#include <trace/events/btrfs.h>
-#include <asm/unaligned.h>
 #include <linux/pagemap.h>
-#include <linux/btrfs.h>
-#include <linux/btrfs_tree.h>
-#include <linux/workqueue.h>
-#include <linux/security.h>
-#include <linux/sizes.h>
-#include <linux/dynamic_debug.h>
-#include <linux/refcount.h>
-#include <linux/crc32c.h>
-#include <linux/iomap.h>
-#include <linux/fscrypt.h>
-#include "extent-io-tree.h"
-#include "extent_io.h"
-#include "extent_map.h"
-#include "async-thread.h"
-#include "block-rsv.h"
 #include "locking.h"
-#include "misc.h"
 #include "fs.h"
 
 struct btrfs_trans_handle;
-- 
2.41.0


  parent reply	other threads:[~2023-08-25 20:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 20:19 [PATCH v2 00/12] btrfs: ctree.[ch] cleanups Josef Bacik
2023-08-25 20:19 ` [PATCH v2 01/12] btrfs: move btrfs_crc32c_final into free-space-cache.c Josef Bacik
2023-08-25 20:19 ` [PATCH v2 02/12] btrfs: remove btrfs_crc32c wrapper Josef Bacik
2023-08-25 20:19 ` [PATCH v2 03/12] btrfs: move btrfs_extref_hash into inode-item.h Josef Bacik
2023-08-25 20:19 ` [PATCH v2 04/12] btrfs: move btrfs_name_hash to dir-item.h Josef Bacik
2023-08-25 20:19 ` [PATCH v2 05/12] btrfs: include asm/unaligned.h in accessors.h Josef Bacik
2023-08-25 20:19 ` [PATCH v2 06/12] btrfs: include linux/crc32c in dir-item and inode-item Josef Bacik
2023-08-25 20:19 ` [PATCH v2 07/12] btrfs: include linux/iomap.h in file.c Josef Bacik
2023-08-25 20:19 ` [PATCH v2 08/12] btrfs: add fscrypt related dependencies to respective headers Josef Bacik
2023-08-25 20:19 ` [PATCH v2 09/12] btrfs: add btrfs_delayed_ref_head declaration to extent-tree.h Josef Bacik
2023-08-25 20:19 ` [PATCH v2 10/12] btrfs: include trace header in where necessary Josef Bacik
2023-08-25 20:19 ` [PATCH v2 11/12] btrfs: include linux/security.h in super.c Josef Bacik
2023-08-25 20:19 ` Josef Bacik [this message]
2023-09-05 13:44   ` [PATCH v2 12/12] btrfs: remove extraneous includes from ctree.h David Sterba
2023-08-28 16:25 ` [PATCH v2 00/12] btrfs: ctree.[ch] cleanups Johannes Thumshirn
2023-09-05 13:45   ` David Sterba
2023-09-05 14:38 ` David Sterba

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=15d63abd06cb64b7edc83d033e65ca00a2bae3ba.1692994620.git.josef@toxicpanda.com \
    --to=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).