Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>, linux-xfs@vger.kernel.org
Subject: [PATCH 2/4] xfs: include <linux/iversion.h> in xfs_platform.h
Date: Fri, 25 Sep 2026 17:18:27 +0200	[thread overview]
Message-ID: <20260925151841.3385994-3-hch@lst.de> (raw)
In-Reply-To: <20260925151841.3385994-1-hch@lst.de>

This removes the only non-xfs inludes from libxfs/ and thus reduces the
differences between the kernel and userspace versions of these files.

Signed-off-by: Christoph Hellwig <hch@lst.de>
---
 fs/xfs/libxfs/xfs_inode_buf.c   | 2 --
 fs/xfs/libxfs/xfs_inode_util.c  | 1 -
 fs/xfs/libxfs/xfs_trans_inode.c | 2 --
 fs/xfs/xfs_platform.h           | 1 +
 4 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/fs/xfs/libxfs/xfs_inode_buf.c b/fs/xfs/libxfs/xfs_inode_buf.c
index b82f067ca5b1..282e78e5e3e8 100644
--- a/fs/xfs/libxfs/xfs_inode_buf.c
+++ b/fs/xfs/libxfs/xfs_inode_buf.c
@@ -20,8 +20,6 @@
 #include "xfs_health.h"
 #include "xfs_metafile.h"
 
-#include <linux/iversion.h>
-
 /*
  * If we are doing readahead on an inode buffer, we might be in log recovery
  * reading an inode allocation buffer that hasn't yet been replayed, and hence
diff --git a/fs/xfs/libxfs/xfs_inode_util.c b/fs/xfs/libxfs/xfs_inode_util.c
index 258ac3d0d486..16c4c2ccdbb8 100644
--- a/fs/xfs/libxfs/xfs_inode_util.c
+++ b/fs/xfs/libxfs/xfs_inode_util.c
@@ -3,7 +3,6 @@
  * Copyright (c) 2000-2006 Silicon Graphics, Inc.
  * All Rights Reserved.
  */
-#include <linux/iversion.h>
 #include "xfs_platform.h"
 #include "xfs_fs.h"
 #include "xfs_shared.h"
diff --git a/fs/xfs/libxfs/xfs_trans_inode.c b/fs/xfs/libxfs/xfs_trans_inode.c
index 1a0fdcbf39fa..e3dca0652d26 100644
--- a/fs/xfs/libxfs/xfs_trans_inode.c
+++ b/fs/xfs/libxfs/xfs_trans_inode.c
@@ -15,8 +15,6 @@
 #include "xfs_trans_priv.h"
 #include "xfs_inode_item.h"
 
-#include <linux/iversion.h>
-
 /*
  * Add a locked inode to the transaction.
  *
diff --git a/fs/xfs/xfs_platform.h b/fs/xfs/xfs_platform.h
index 745d715b4c64..7b63ea26b186 100644
--- a/fs/xfs/xfs_platform.h
+++ b/fs/xfs/xfs_platform.h
@@ -50,6 +50,7 @@
 #include <linux/xattr.h>
 #include <linux/mnt_idmapping.h>
 #include <linux/debugfs.h>
+#include <linux/iversion.h>
 #include <asm/page.h>
 #include <asm/div64.h>
 #include <asm/param.h>
-- 
2.53.0


  parent reply	other threads:[~2026-09-25 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 15:18 small cleanups to help code sharing with xfsprogs Christoph Hellwig
2026-09-25 15:18 ` [PATCH 1/4] xfs: remove various unused includes in libxfs/ Christoph Hellwig
2026-09-25 15:18 ` Christoph Hellwig [this message]
2026-09-25 15:18 ` [PATCH 3/4] xfs: move xfs_*_item.h to libxfs Christoph Hellwig
2026-09-25 15:18 ` [PATCH 4/4] xfs: move xfs_trans.h " Christoph Hellwig
2026-09-25 22:52 ` small cleanups to help code sharing with xfsprogs Darrick J. Wong
2026-09-26  6:06   ` Christoph Hellwig
2026-10-05 10:02     ` Carlos Maiolino
2026-10-08 13:32 ` Carlos Maiolino

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=20260925151841.3385994-3-hch@lst.de \
    --to=hch@lst.de \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@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