From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
ocfs2-devel@oss.oracle.com
Subject: [PATCH 17/24] ocfs2: Convert use of typedef ctl_table to struct ctl_table
Date: Tue, 22 Oct 2013 15:30:00 -0700 [thread overview]
Message-ID: <f5f72664f6f5b3b433149e515cacbd0d90bf99f9.1382480758.git.joe@perches.com> (raw)
In-Reply-To: <cover.1382480758.git.joe@perches.com>
This typedef is unnecessary and should just be removed.
Signed-off-by: Joe Perches <joe@perches.com>
---
fs/ocfs2/stackglue.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/ocfs2/stackglue.c b/fs/ocfs2/stackglue.c
index 39abf89..cb7ec0b 100644
--- a/fs/ocfs2/stackglue.c
+++ b/fs/ocfs2/stackglue.c
@@ -643,7 +643,7 @@ error:
#define FS_OCFS2_NM 1
-static ctl_table ocfs2_nm_table[] = {
+static struct ctl_table ocfs2_nm_table[] = {
{
.procname = "hb_ctl_path",
.data = ocfs2_hb_ctl_path,
@@ -654,7 +654,7 @@ static ctl_table ocfs2_nm_table[] = {
{ }
};
-static ctl_table ocfs2_mod_table[] = {
+static struct ctl_table ocfs2_mod_table[] = {
{
.procname = "nm",
.data = NULL,
@@ -665,7 +665,7 @@ static ctl_table ocfs2_mod_table[] = {
{ }
};
-static ctl_table ocfs2_kern_table[] = {
+static struct ctl_table ocfs2_kern_table[] = {
{
.procname = "ocfs2",
.data = NULL,
@@ -676,7 +676,7 @@ static ctl_table ocfs2_kern_table[] = {
{ }
};
-static ctl_table ocfs2_root_table[] = {
+static struct ctl_table ocfs2_root_table[] = {
{
.procname = "fs",
.data = NULL,
--
1.8.1.2.459.gbcd45b4.dirty
next prev parent reply other threads:[~2013-10-22 22:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 22:29 [PATCH 00/24] treewide: Convert use of typedef ctl_table to struct ctl_table Joe Perches
2013-10-22 22:29 ` [PATCH 01/24] arm: " Joe Perches
2013-10-22 22:29 ` [PATCH 02/24] ia64: " Joe Perches
2013-10-22 22:29 ` [PATCH 03/24] s390: " Joe Perches
2013-10-25 7:18 ` Heiko Carstens
2013-10-22 22:29 ` [PATCH 04/24] tile: " Joe Perches
2013-10-22 22:29 ` [PATCH 05/24] cdrom: " Joe Perches
2013-10-22 22:29 ` [PATCH 06/24] random: " Joe Perches
2013-10-22 22:29 ` [PATCH 07/24] infiniband: " Joe Perches
2013-10-22 22:29 ` [PATCH 08/24] md: " Joe Perches
2013-10-23 0:37 ` NeilBrown
2013-10-22 22:29 ` [PATCH 09/24] parport: " Joe Perches
2013-10-22 22:29 ` [PATCH 10/24] scsi: " Joe Perches
2013-10-22 22:29 ` [PATCH 11/24] coda: " Joe Perches
2013-10-22 22:29 ` [PATCH 12/24] fscache: " Joe Perches
2013-10-22 22:29 ` [PATCH 13/24] lockd: " Joe Perches
2013-10-22 22:29 ` [PATCH 14/24] nfs: " Joe Perches
2013-10-22 22:29 ` [PATCH 15/24] inotify: " Joe Perches
2013-10-22 22:29 ` [PATCH 16/24] ntfs: " Joe Perches
2013-10-22 22:30 ` Joe Perches [this message]
2013-11-07 11:06 ` [PATCH 17/24] ocfs2: " Joel Becker
2013-10-22 22:30 ` [PATCH 18/24] proc: " Joe Perches
2013-10-22 22:30 ` [PATCH 19/24] fs: " Joe Perches
2013-10-22 22:30 ` [PATCH 20/24] key: " Joe Perches
2013-10-22 22:30 ` [PATCH 21/24] ipc: " Joe Perches
2013-10-22 22:30 ` [PATCH 22/24] kernel: " Joe Perches
2013-10-22 22:30 ` [PATCH 23/24] mm: " Joe Perches
2013-10-22 22:30 ` [PATCH 24/24] security:keys: " Joe Perches
2013-10-22 23:53 ` [PATCH 00/24] treewide: " David Daney
2013-10-22 23:58 ` Joe Perches
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=f5f72664f6f5b3b433149e515cacbd0d90bf99f9.1382480758.git.joe@perches.com \
--to=joe@perches.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.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).