archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley-RxcU5blhW6jCXq6kfMZ53/>
To: Peter Huewe <>,
	James Morris <jmorris-gx6/>
Cc: Jason Gunthorpe
	George Wilson <gcwilson-r/>,,
	Mimi Zohar
	Jarkko Sakkinen
Subject: Re: Future of TPMDD @ Linux Security Summit / Plumbers
Date: Wed, 13 Sep 2017 13:51:20 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <trinity-ab47fab5-3247-446f-add3-baebe7c51350-1505335723429@3c-app-gmx-bs26>

On September 13, 2017 1:48:43 PM PST, Peter Huewe <> wrote:
>Hi Jarkko, Mimi, James, Jason, and everybody else,
>it would be great if we could find a slot to discuss in person how we
>proceed with the mailing lists, patch flows and review cycles.
>I know there were some discussions, but atleast for my part I did not
>get the final conclusion on how we proceed and why.
>Also I would like to discuss what is the current status of the move to
> infrastructure (or atleast away from sf), and maybe we can
>find anyone here at Plumbers to remove any blocking points.
>Maybe we could also discuss how we can improve our testing strategy and
>discuss which tests currently exists.
>We have a (semi-)automatic test environment for the tpm kernel patches
>at work and we are currently exploring how to expand this further and
>automate it completely. I can give you a quick rundown on this if

At plumbers we could do a lunch meeting, a hack room session,a bof or an unconference.  Take your pick.


>Check out the vibrant tech community on one of the world's most
>engaging tech sites,!
>tpmdd-devel mailing list

Sent from my Android device with K-9 Mail. Please excuse my brevity.

Check out the vibrant tech community on one of the world's most
engaging tech sites,!
tpmdd-devel mailing list

  reply	other threads:[~2017-09-13 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
     [not found]         ` <>
     [not found]           ` <>
     [not found]             ` <>
     [not found]               ` <>
     [not found]                 ` <>
     [not found]                   ` <>
     [not found]                     ` <>
     [not found]                       ` <alpine.LRH.2.20.1708300003510.19193-gx6/>
2017-09-13 20:48                         ` Future of TPMDD @ Linux Security Summit / Plumbers Peter Huewe
2017-09-13 20:51                           ` James Bottomley [this message]
2017-09-13 23:21                           ` Jarkko Sakkinen
     [not found]                             ` <20170913232125.7e2cmsycxhb376z7-VuQAYsv1563Yd54FQh9/>
2017-09-13 23:52                               ` Peter Huewe

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \
    --to=james.bottomley-rxcu5blhw6jcxq6kfmz53/ \ \
    --cc=gcwilson-r/ \
    --cc=jarkko.sakkinen-VuQAYsv1563Yd54FQh9/ \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/ \
    --cc=jmorris-gx6/ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).