From: Dave Hansen <dave.hansen@intel.com>
To: linux-coco@lists.linux.dev, "Shutemov,
Kirill" <kirill.shutemov@intel.com>
Subject: x86/coco MAINTAINERS mailing list
Date: Thu, 7 Apr 2022 11:05:07 -0700 [thread overview]
Message-ID: <15499854-3806-3333-159b-56e8f494cf17@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
Hi coco folks,
There are some x86-specific "coco" additions being proposed here:
> https://lore.kernel.org/all/b43720c6-0763-f4bb-64a0-7745c6ad920a@intel.com/
that we're thinking about merging some time soon. They add some
"arch/x86/coco/" files:
> arch/x86/coco/Makefile | 2 +
> arch/x86/coco/core.c | 22 +-
> arch/x86/coco/tdx/Makefile | 3 +
> arch/x86/coco/tdx/tdcall.S | 204 +++++++
> arch/x86/coco/tdx/tdx.c | 692 +++++++++++++++++++++++
It would be nice to have a MAINTAINERS entry for these. I know this
list is ideally arch-agnostic, but would anyone mind if it is listed as
the x86/coco mailing list? Maybe something like the attached patch.
[-- Attachment #2: x86-coco.patch --]
[-- Type: text/x-patch, Size: 470 bytes --]
diff --git a/MAINTAINERS b/MAINTAINERS
index fd768d43e048..f8fa4786cc3d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10807,6 +10807,13 @@ F: arch/x86/kernel/kvmclock.c
F: arch/x86/kvm/
F: arch/x86/kvm/*/
+X86 CONFIDENTIAL COMPUTING
+M: x86@kernel.org
+R: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
+L: linux-coco@lists.linux.dev
+S: Supported
+F: arch/x86/coco/
+
KERNFS
M: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
M: Tejun Heo <tj@kernel.org>
reply other threads:[~2022-04-07 18:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=15499854-3806-3333-159b-56e8f494cf17@intel.com \
--to=dave.hansen@intel.com \
--cc=kirill.shutemov@intel.com \
--cc=linux-coco@lists.linux.dev \
/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.