From: tip-bot for Will Deacon <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, will.deacon@arm.com, mingo@kernel.org,
jason.low2@hpe.com, joe@perches.com, peterz@infradead.org,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de
Subject: [tip:locking/urgent] MAINTAINERS: Remove dead path from LOCKING PRIMITIVES entry
Date: Tue, 2 Oct 2018 03:15:56 -0700 [thread overview]
Message-ID: <tip-6d348925b306ab0cc9757a09a8cea6bf288018e4@git.kernel.org> (raw)
In-Reply-To: <20181001142856.GC9716@arm.com>
Commit-ID: 6d348925b306ab0cc9757a09a8cea6bf288018e4
Gitweb: https://git.kernel.org/tip/6d348925b306ab0cc9757a09a8cea6bf288018e4
Author: Will Deacon <will.deacon@arm.com>
AuthorDate: Mon, 1 Oct 2018 15:28:56 +0100
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Tue, 2 Oct 2018 10:45:57 +0200
MAINTAINERS: Remove dead path from LOCKING PRIMITIVES entry
Since 890658b7ab48 ("locking/mutex: Kill arch specific code"), there
are no mutex header files under arch/, so we can remove the redundant
entry from MAINTAINERS.
Reported-by: Joe Perches <joe@perches.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Cc: Jason Low <jason.low2@hpe.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/20181001142856.GC9716@arm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a255240d1452..3bd8913b2d78 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8598,7 +8598,6 @@ F: include/linux/spinlock*.h
F: arch/*/include/asm/spinlock*.h
F: include/linux/rwlock*.h
F: include/linux/mutex*.h
-F: arch/*/include/asm/mutex*.h
F: include/linux/rwsem*.h
F: arch/*/include/asm/rwsem.h
F: include/linux/seqlock.h
prev parent reply other threads:[~2018-10-02 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 21:54 Bad MAINTAINERS pattern in section 'LOCKING PRIMITIVES' Joe Perches
2018-10-01 14:28 ` Will Deacon
2018-10-02 10:15 ` tip-bot for Will Deacon [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-6d348925b306ab0cc9757a09a8cea6bf288018e4@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=jason.low2@hpe.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 \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.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
Powered by JetHome