public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ferry Meng <mengferry@linux.alibaba.com>
To: linux-erofs@lists.ozlabs.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ferry Meng <mengferry@linux.alibaba.com>
Subject: [PATCH 3/3] erofs: remove redundant erofs_fs_type declaration in super.c
Date: Tue, 15 Aug 2023 17:48:49 +0800	[thread overview]
Message-ID: <20230815094849.53249-3-mengferry@linux.alibaba.com> (raw)
In-Reply-To: <20230815094849.53249-1-mengferry@linux.alibaba.com>

As erofs_fs_type has been declared in internal.h, there is no use to
declare repeatedly in super.c.

Signed-off-by: Ferry Meng <mengferry@linux.alibaba.com>
---
 fs/erofs/super.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/fs/erofs/super.c b/fs/erofs/super.c
index 82f41d09f8d8..78a94955dd61 100644
--- a/fs/erofs/super.c
+++ b/fs/erofs/super.c
@@ -19,7 +19,6 @@
 #include <trace/events/erofs.h>
 
 static struct kmem_cache *erofs_inode_cachep __read_mostly;
-struct file_system_type erofs_fs_type;
 
 void _erofs_err(struct super_block *sb, const char *func, const char *fmt, ...)
 {
-- 
2.19.1.6.gb485710b


  parent reply	other threads:[~2023-08-15  9:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15  9:48 [PATCH 1/3] erofs: clean up redundant comment and adjust code alignment Ferry Meng
2023-08-15  9:48 ` [PATCH 2/3] erofs: add necessary kmem_cache_create flags for erofs inode cache Ferry Meng
2023-08-15 15:13   ` Gao Xiang
2023-08-23 14:45   ` Chao Yu
2023-08-15  9:48 ` Ferry Meng [this message]
2023-08-15 15:15   ` [PATCH 3/3] erofs: remove redundant erofs_fs_type declaration in super.c Gao Xiang
2023-08-23 14:46   ` Chao Yu
2023-08-15 15:14 ` [PATCH 1/3] erofs: clean up redundant comment and adjust code alignment Gao Xiang
2023-08-15 15:15 ` Gao Xiang
2023-08-23 14:38 ` Chao Yu

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=20230815094849.53249-3-mengferry@linux.alibaba.com \
    --to=mengferry@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@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