From: "gnehzuil.liu@gmail.com" <gnehzuil.liu@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: Zheng Liu <wenqing.lz@taobao.com>
Subject: [PATCH] ext4: remove duplicated declarations in inode.c
Date: Wed, 6 Jun 2012 21:03:22 +0800 [thread overview]
Message-ID: <1338987802-10186-1-git-send-email-gnehzuil.liu@gmail.com> (raw)
From: Zheng Liu <wenqing.lz@taobao.com>
in patch cb20d5188366f04d96d2e07b1240cc92170ade40, ext4_set_bh_endio and
ext4_end_io_buffer_write are declared at the beginning of inode.c file. So we
can remove duplicated declarations in this file.
Signed-off-by: Zheng Liu <wenqing.lz@taobao.com>
---
fs/ext4/inode.c | 3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index 02bc8cb..dd0fa3c 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -1925,9 +1925,6 @@ out:
return ret;
}
-static int ext4_set_bh_endio(struct buffer_head *bh, struct inode *inode);
-static void ext4_end_io_buffer_write(struct buffer_head *bh, int uptodate);
next reply other threads:[~2012-06-06 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 13:03 gnehzuil.liu [this message]
2012-08-19 22:10 ` [PATCH] ext4: remove duplicated declarations in inode.c Theodore Ts'o
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=1338987802-10186-1-git-send-email-gnehzuil.liu@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=wenqing.lz@taobao.com \
/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).