From: tip-bot for Namhyung Kim <namhyung@kernel.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
peterz@infradead.org, tglx@linutronix.de, namhyung@kernel.org
Subject: [tip:sched/urgent] MAINTAINERS/sched: Update scheduler file pattern
Date: Fri, 6 Jul 2012 06:47:20 -0700 [thread overview]
Message-ID: <tip-95c0d71dcb853c2eca5f2231ebbd4c1d3af775b7@git.kernel.org> (raw)
In-Reply-To: <1341326251-4140-1-git-send-email-namhyung@kernel.org>
Commit-ID: 95c0d71dcb853c2eca5f2231ebbd4c1d3af775b7
Gitweb: http://git.kernel.org/tip/95c0d71dcb853c2eca5f2231ebbd4c1d3af775b7
Author: Namhyung Kim <namhyung@kernel.org>
AuthorDate: Tue, 3 Jul 2012 23:37:31 +0900
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Fri, 6 Jul 2012 12:55:35 +0200
MAINTAINERS/sched: Update scheduler file pattern
The commit 391e43da797a ("sched: Move all scheduler bits into
kernel/sched/") moved all scheduler codes to the kernel/sched/
directory, but missed the MAINTAINERS. Since it still expects
files from kernel/ directory, get_maintainer script has to rely
on the git (log) fallback mechanism.
$ scripts/get_maintainer.pl -f kernel/sched/core.c --nogit-fallback
linux-kernel@vger.kernel.org (open list)
With this patch:
$ scripts/get_maintainer.pl -f kernel/sched/core.c --nogit-fallback
Ingo Molnar <mingo@redhat.com> (maintainer:SCHEDULER)
Peter Zijlstra <peterz@infradead.org> (maintainer:SCHEDULER)
linux-kernel@vger.kernel.org (open list)
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Acked-by: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1341326251-4140-1-git-send-email-namhyung@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
MAINTAINERS | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 03df1d1..214d754 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5909,7 +5909,7 @@ M: Ingo Molnar <mingo@redhat.com>
M: Peter Zijlstra <peterz@infradead.org>
T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
S: Maintained
-F: kernel/sched*
+F: kernel/sched/
F: include/linux/sched.h
SCORE ARCHITECTURE
prev parent reply other threads:[~2012-07-06 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 14:37 [PATCH] MAINTAINERS: " Namhyung Kim
2012-07-06 13:47 ` tip-bot for Namhyung Kim [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-95c0d71dcb853c2eca5f2231ebbd4c1d3af775b7@git.kernel.org \
--to=namhyung@kernel.org \
--cc=hpa@zytor.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
all inboxes | Powered by JetHome®