From: tip-bot for Joe Perches <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
joe@perches.com, peterz@infradead.org, tglx@linutronix.de
Subject: [tip:sched/core] sched: Don' t mix use of typedef ctl_table and struct ctl_table
Date: Wed, 19 Jun 2013 11:41:20 -0700 [thread overview]
Message-ID: <tip-be7002e6c613d22976f2b8d4bae6121a5fc0433a@git.kernel.org> (raw)
In-Reply-To: <1371063336.2069.22.camel@joe-AO722>
Commit-ID: be7002e6c613d22976f2b8d4bae6121a5fc0433a
Gitweb: http://git.kernel.org/tip/be7002e6c613d22976f2b8d4bae6121a5fc0433a
Author: Joe Perches <joe@perches.com>
AuthorDate: Wed, 12 Jun 2013 11:55:36 -0700
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 19 Jun 2013 12:58:48 +0200
sched: Don't mix use of typedef ctl_table and struct ctl_table
Just use struct ctl_table.
Signed-off-by: Joe Perches <joe@perches.com>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1371063336.2069.22.camel@joe-AO722
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/sched/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 21b1403..ceeaf0f 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -4533,7 +4533,7 @@ sd_alloc_ctl_domain_table(struct sched_domain *sd)
return table;
}
-static ctl_table *sd_alloc_ctl_cpu_table(int cpu)
+static struct ctl_table *sd_alloc_ctl_cpu_table(int cpu)
{
struct ctl_table *entry, *table;
struct sched_domain *sd;
prev parent reply other threads:[~2013-06-19 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 18:55 [PATCH] sched: core: Don't " Joe Perches
2013-06-19 18:41 ` tip-bot for Joe Perches [this message]
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=tip-be7002e6c613d22976f2b8d4bae6121a5fc0433a@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.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
Powered by JetHome