From: "tip-bot2 for Muhammad Usama Anjum" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/misc] MAINTAINERS: Add selftests/x86 entry
Date: Wed, 28 Aug 2024 17:45:51 -0000 [thread overview]
Message-ID: <172486715194.2215.8525924173701820802.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240610052810.1488793-1-usama.anjum@collabora.com>
The following commit has been merged into the x86/misc branch of tip:
Commit-ID: 4460e8538ef17c86eae46ccbe096eee8c740a7d0
Gitweb: https://git.kernel.org/tip/4460e8538ef17c86eae46ccbe096eee8c740a7d0
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
AuthorDate: Mon, 10 Jun 2024 10:28:10 +05:00
Committer: Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Wed, 28 Aug 2024 19:32:47 +02:00
MAINTAINERS: Add selftests/x86 entry
There are no maintainers specified for tools/testing/selftests/x86. Shuah has
mentioned [1] that the patches should go through x86 tree or in special cases
directly to Shuah's tree after getting ack-ed from x86 maintainers. Different
people have been confused when sending patches as correct maintainers aren't
found by get_maintainer.pl script. Fix this by adding entry to MAINTAINERS
file.
[1] https://lore.kernel.org/all/90dc0dfc-4c67-4ea1-b705-0585d6e2ec47@linuxfoundation.org
Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Acked-by: Dave Hansen <dave.hansen@linux.intel.com>
Link: https://lore.kernel.org/r/20240610052810.1488793-1-usama.anjum@collabora.com
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6daab3f..7715a80 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -24772,6 +24772,7 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/core
F: Documentation/arch/x86/
F: Documentation/devicetree/bindings/x86/
F: arch/x86/
+F: tools/testing/selftests/x86
X86 CPUID DATABASE
M: Borislav Petkov <bp@alien8.de>
prev parent reply other threads:[~2024-08-28 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 5:28 [PATCH] " Muhammad Usama Anjum
2024-07-02 10:17 ` Muhammad Usama Anjum
2024-07-31 13:42 ` Muhammad Usama Anjum
2024-07-31 18:14 ` Shuah Khan
2024-07-31 21:23 ` Peter Zijlstra
2024-08-01 19:27 ` Shuah Khan
2024-08-01 19:57 ` Shuah Khan
2024-08-28 17:18 ` Dave Hansen
2024-08-28 17:45 ` tip-bot2 for Muhammad Usama Anjum [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=172486715194.2215.8525924173701820802.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=usama.anjum@collabora.com \
--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®