From: "tip-bot2 for Christophe JAILLET" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Ingo Molnar <mingo@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: locking/core] MAINTAINERS: Add include/linux/lockdep*.h
Date: Sun, 26 Nov 2023 10:01:09 -0000 [thread overview]
Message-ID: <170099286957.398.270163389762223415.tip-bot2@tip-bot2> (raw)
In-Reply-To: =?utf-8?q?=3Ce722abd043e5de64d2acd28d581e4a952994a94e=2E17009?= =?utf-8?q?89248=2Egit=2Echristophe=2Ejaillet=40wanadoo=2Efr=3E?=
The following commit has been merged into the locking/core branch of tip:
Commit-ID: a0c8711b1da5cb62ba50b96b4e7991f03073f477
Gitweb: https://git.kernel.org/tip/a0c8711b1da5cb62ba50b96b4e7991f03073f477
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
AuthorDate: Sun, 26 Nov 2023 10:00:59 +01:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Sun, 26 Nov 2023 10:53:29 +01:00
MAINTAINERS: Add include/linux/lockdep*.h
Have lockdep_api.h and lockdep_types.h match as well.
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/e722abd043e5de64d2acd28d581e4a952994a94e.1700989248.git.christophe.jaillet@wanadoo.fr
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 97f51d5..9834adc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12458,7 +12458,7 @@ S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
F: Documentation/locking/
F: arch/*/include/asm/spinlock*.h
-F: include/linux/lockdep.h
+F: include/linux/lockdep*.h
F: include/linux/mutex*.h
F: include/linux/rwlock*.h
F: include/linux/rwsem*.h
next reply other threads:[~2023-11-26 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 10:01 tip-bot2 for Christophe JAILLET [this message]
2023-11-27 8:53 tip-bot2 for Christophe JAILLET
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=170099286957.398.270163389762223415.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.org \
/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®