From: James Bottomley <James.Bottomley-RxcU5blhW6jCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
To: Peter Huewe <PeterHuewe-Mmb7MZpHnFY@public.gmane.org>,
James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
Cc: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
George Wilson <gcwilson-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Mimi Zohar
<zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
Jarkko Sakkinen
<jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: Re: Future of TPMDD @ Linux Security Summit / Plumbers
Date: Wed, 13 Sep 2017 13:51:20 -0700 [thread overview]
Message-ID: <df7c2d96-8790-4625-a6d1-7ba06d691e57@email.android.com> (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 <PeterHuewe@gmx.de> 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
>kernel.org 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
>interested.
At plumbers we could do a lunch meeting, a hack room session,a bof or an unconference. Take your pick.
James
>
>Thanks,
>Peter
>
>------------------------------------------------------------------------------
>Check out the vibrant tech community on one of the world's most
>engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>_______________________________________________
>tpmdd-devel mailing list
>tpmdd-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
--
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, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
tpmdd-devel mailing list
tpmdd-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
next prev parent reply other threads:[~2017-09-13 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1503697721.4203.151.camel@linux.vnet.ibm.com>
[not found] ` <20170825220252.uuy43ryhuavoz2jq@linux.intel.com>
[not found] ` <20170825220416.h2j2sns72kukf466@linux.intel.com>
[not found] ` <1503699356.4203.159.camel@linux.vnet.ibm.com>
[not found] ` <20170825222209.GA22199@obsidianresearch.com>
[not found] ` <1503703596.8359.6.camel@linux.vnet.ibm.com>
[not found] ` <20170826074135.mx3i3bo6b3lrevdu@linux.intel.com>
[not found] ` <20170826074843.isaxpmrotyk46u6j@linux.intel.com>
[not found] ` <1503847647.5847.51.camel@linux.vnet.ibm.com>
[not found] ` <alpine.LRH.2.20.1708281126230.3474@namei.org>
[not found] ` <20170829121137.ovgkrcihgy5jcufu@linux.intel.com>
[not found] ` <alpine.LRH.2.20.1708300003510.19193@namei.org>
[not found] ` <alpine.LRH.2.20.1708300003510.19193-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
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/CA@public.gmane.org>
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:
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=df7c2d96-8790-4625-a6d1-7ba06d691e57@email.android.com \
--to=james.bottomley-rxcu5blhw6jcxq6kfmz53/egyhegw8jk@public.gmane.org \
--cc=PeterHuewe-Mmb7MZpHnFY@public.gmane.org \
--cc=gcwilson-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).