Linux-Integrity Archive on lore.kernel.org
 help / color / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-integrity@vger.kernel.org
Cc: zohar@linux.ibm.com, jejb@linux.ibm.com, dhowells@redhat.com,
	sumit.garg@linaro.org
Subject: KEYS-TRUSTED git
Date: Sun, 08 Sep 2019 03:10:23 +0300
Message-ID: <c253ca7292b397f1352d2ee00fce0b011f84abff.camel@linux.intel.com> (raw)

It seems that at least vast majority of the trusted keys patches flow
through my tree to the mainline. Still, it is undocumented in the
MAINTAINERS file.

So, should I just add my TPM tree as the upstream there? Or should I
just create a new GIT for trusted keys? My TPM PR goes to Linux ATM.
Should my trusted keys PR go to David instead? That would definitely
require own tree.

With Sumit's recent work trusted keys is turning more than just being
TPM keys so now it is a good time to consider the flow... Sumit, I'm
sorry that I haven't added your first series yet. I need to first sync
up how we are going to move forward.

/Jarkko


             reply index

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08  0:10 Jarkko Sakkinen [this message]
2019-09-08 14:20 ` Mimi Zohar
2019-09-09  6:27   ` Sumit Garg
2019-09-09 10:40     ` Mimi Zohar
2019-09-09 16:36     ` Jarkko Sakkinen
2019-09-10  5:13       ` Sumit Garg
2019-09-13 13:34         ` Jarkko Sakkinen
2019-09-10 11:43     ` Jarkko Sakkinen
2019-09-10 12:32       ` Sumit Garg
2019-09-11  9:27       ` Jarkko Sakkinen
2019-09-11  9:29         ` Jarkko Sakkinen
2019-09-11  9:36           ` Jarkko Sakkinen
2019-09-11  9:58             ` Sumit Garg
2019-09-11 11:28               ` Sumit Garg
2019-09-09 16:33   ` Jarkko Sakkinen
2019-09-09 16:52   ` Jarkko Sakkinen
2019-09-09 17:24     ` Mimi Zohar
2019-09-13 13:32       ` Jarkko Sakkinen
2019-09-15 20:53         ` Mimi Zohar
2019-09-10 14:21     ` 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=c253ca7292b397f1352d2ee00fce0b011f84abff.camel@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=dhowells@redhat.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=sumit.garg@linaro.org \
    --cc=zohar@linux.ibm.com \
    /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

Linux-Integrity Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-integrity/0 linux-integrity/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-integrity linux-integrity/ https://lore.kernel.org/linux-integrity \
		linux-integrity@vger.kernel.org
	public-inbox-index linux-integrity

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-integrity


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git