linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: [PATCH 08/24] md: Convert use of typedef ctl_table to struct ctl_table
Date: Tue, 22 Oct 2013 15:29:51 -0700	[thread overview]
Message-ID: <97bd203891c6b2c45b2e77c31edda1b4149782f2.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>
---
 drivers/md/md.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/md/md.c b/drivers/md/md.c
index 8a0d762..7b57639 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -112,7 +112,7 @@ static inline int speed_max(struct mddev *mddev)
 
 static struct ctl_table_header *raid_table_header;
 
-static ctl_table raid_table[] = {
+static struct ctl_table raid_table[] = {
 	{
 		.procname	= "speed_limit_min",
 		.data		= &sysctl_speed_limit_min,
@@ -130,7 +130,7 @@ static ctl_table raid_table[] = {
 	{ }
 };
 
-static ctl_table raid_dir_table[] = {
+static struct ctl_table raid_dir_table[] = {
 	{
 		.procname	= "raid",
 		.maxlen		= 0,
@@ -140,7 +140,7 @@ static ctl_table raid_dir_table[] = {
 	{ }
 };
 
-static ctl_table raid_root_table[] = {
+static struct ctl_table raid_root_table[] = {
 	{
 		.procname	= "dev",
 		.maxlen		= 0,
-- 
1.8.1.2.459.gbcd45b4.dirty


  parent reply	other threads:[~2013-10-22 22:30 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 ` Joe Perches [this message]
2013-10-23  0:37   ` [PATCH 08/24] md: " 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 ` [PATCH 17/24] ocfs2: " Joe Perches
2013-11-07 11:06   ` 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=97bd203891c6b2c45b2e77c31edda1b4149782f2.1382480758.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).