mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: "Camacho Romero, Michal" <michal.camacho.romero@intel.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"bp@alien8.de" <bp@alien8.de>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"Mowka, Mateusz" <mateusz.mowka@intel.com>,
	"Pawlicki, AdamX" <adamx.pawlicki@intel.com>
Cc: "Michalak, BartlomiejX" <bartlomiejx.michalak@intel.com>,
	"Fedko, Artem" <artem.fedko@intel.com>,
	"Zielinski, Marcel" <marcel.zielinski@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ning Sun <ning.sun@intel.com>
Subject: Re: [PATCH v1] x86: Change maintainers list for the Intel TXT project group
Date: Wed, 4 Jun 2025 07:00:59 -0700	[thread overview]
Message-ID: <c6c2ef2e-7372-4ce4-9ac6-6a2a60f18093@intel.com> (raw)
In-Reply-To: <IA1PR11MB7755413461E0F4403A702E3AAF6CA@IA1PR11MB7755.namprd11.prod.outlook.com>

On 6/4/25 00:51, Camacho Romero, Michal wrote:
> I’m BIOS Engineer from the Intel Corp, working on the BIOS security 
> modules development, including TBOOT MLE project: As the present
> INTEL(R) TRUSTED EXECUTION TECHNOLOGY (TXT) group's maintainer (Ning
> Sun) doesn't work currently on the TBOOT project's development, he
> was replaced by the active TBOOT MLE project's developers, who will
> maintain Intel TXT project group and are currently maintaining the
> TBOOT MLE project: http://tboot.sourceforge.net <http://
> tboot.sourceforge.net>

Hi Michal,

For folks to function as effective maintainers, they need to be able to
review and submit patches. This patch wasn't submitted following our
normal processes:

> https://www.kernel.org/doc/Documentation/process/submitting-patches.rst

It came to me quite mangled, and was likely dropped from the mailing
lists because of the HTML.

The easiest way to do it these days is probably to just use
git-send-email. But if you're going to be an effective maintainer,
you'll need to get your email setup sorted sooner or later. That means
no Outlook.

It's also normal to cc the person who is being replaced, or even after
they've moved on to other jobs.

Since there are three of you, could you please go take a look at this
"trenchboot" stuff? Their aim seems to be to duplicate some of what
tboot can be used for, and they expect to leverage TXT itself:

>
https://lore.kernel.org/all/18F9BD47-282D-4225-AB6B-FDA4AD52D7AE@gmail.com/

If nothing else, it would be great to know if you folks think trenchboot
is the way forward and what the future of the tboot code in the kernel
is if trenchboot is also there.

Oh, and again since there are three of you...  first link in:

	Documentation/arch/x86/intel_txt.rst

gets a 404. That would be a nice thing to fix up first, I think. Maybe
you can send a fix for that along with the fixed MAINTAINERS update.



           reply	other threads:[~2025-06-04 14:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <IA1PR11MB7755413461E0F4403A702E3AAF6CA@IA1PR11MB7755.namprd11.prod.outlook.com>]

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=c6c2ef2e-7372-4ce4-9ac6-6a2a60f18093@intel.com \
    --to=dave.hansen@intel.com \
    --cc=adamx.pawlicki@intel.com \
    --cc=artem.fedko@intel.com \
    --cc=bartlomiejx.michalak@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel.zielinski@intel.com \
    --cc=mateusz.mowka@intel.com \
    --cc=michal.camacho.romero@intel.com \
    --cc=mingo@redhat.com \
    --cc=ning.sun@intel.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 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®