From: jarkko@kernel.org
To: linux-kernel@vger.kernel.org
Cc: haitao.huang@intel.com, kai.huang@intel.com,
dave.hansen@intel.com, Jarkko Sakkinen <jarkko@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
Jethro Beekman <jethro@fortanix.com>,
Borislav Petkov <bp@suse.de>
Subject: [PATCH] MAINTAINERS: Fix the T-entry for INTEL SGX
Date: Thu, 21 Jan 2021 04:42:56 +0200 [thread overview]
Message-ID: <20210121024256.54565-1-jarkko@kernel.org> (raw)
From: Jarkko Sakkinen <jarkko@kernel.org>
After a discussion with Boris et al, I've come to realize that a disjoint
GIT tree for SGX does not any sense.
Instead follow the pattern of other MAINTAINERS entries, IRQ DOMAINS for
instance, and re-define T-entry so that it will reference the pre-existing
topic branch for SGX. As Boris explained to me, reviewed patches will be
routinely picked to this branch.
CC: Thomas Gleixner <tglx@linutronix.de>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@redhat.com>
Fixes: bc4bac2ecef0 ("x86/sgx: Update MAINTAINERS")
Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 705776b31c8d..64fb8658aafb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9227,7 +9227,7 @@ M: Jarkko Sakkinen <jarkko@kernel.org>
L: linux-sgx@vger.kernel.org
S: Supported
Q: https://patchwork.kernel.org/project/intel-sgx/list/
-T: git git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-sgx.git
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/sgx
F: Documentation/x86/sgx.rst
F: arch/x86/entry/vdso/vsgx.S
F: arch/x86/include/uapi/asm/sgx.h
--
2.29.2
next reply other threads:[~2021-01-21 2:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 2:42 jarkko [this message]
2021-01-21 13:18 ` [tip: x86/sgx] MAINTAINERS: Fix the tree location for INTEL SGX patches tip-bot2 for Jarkko Sakkinen
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=20210121024256.54565-1-jarkko@kernel.org \
--to=jarkko@kernel.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=haitao.huang@intel.com \
--cc=jethro@fortanix.com \
--cc=kai.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.