From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Matthew Fioravante <matthew.fioravante@jhuapl.edu>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH mini-os enhancements for vtpm 8/8] Add 3 tpm drivers to mini-os
Date: Wed, 26 Sep 2012 23:43:43 +0200 [thread overview]
Message-ID: <20120926214343.GC4407@type> (raw)
In-Reply-To: <CAFLBxZZMR1AdaaJN=BNPsmjYFcFV13RLCwS8_JLFqukfFZy96w@mail.gmail.com>
George Dunlap, le Wed 26 Sep 2012 14:30:23 +0100, a écrit :
> On Tue, Sep 18, 2012 at 7:24 PM, Matthew Fioravante
> <matthew.fioravante@jhuapl.edu> wrote:
> > Is there anyone on the dev list that is familiar enough to review it?
> >
> > I can tell you we have been using all 3 of these drivers internally for
> > about 2 years now without issue. All of them are basically ports of the
> > linux drivers to mini-os.
>
> If you're willing to be the TPM maintainer (which would involve adding
> your name to the MAINTAINERS file), and if Samuel is OK with you
> owning the tpm-related files in stubdom, I think it wouldn't
> necessarily need a thorough review to get in, as long as people are
> happy with how it integrates with the rest of the code. What do
> people think?
I'm completely fine with it.
Samuel
next prev parent reply other threads:[~2012-09-26 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 22:08 [PATCH mini-os enhancements for vtpm 8/8] Add 3 tpm drivers to mini-os Matthew Fioravante
2012-09-17 22:52 ` Samuel Thibault
2012-09-18 18:24 ` Matthew Fioravante
2012-09-26 13:30 ` George Dunlap
2012-09-26 14:31 ` Matthew Fioravante
2012-09-26 21:43 ` Samuel Thibault [this message]
2012-09-19 12:07 ` Ian Campbell
2012-09-19 14:54 ` Matthew Fioravante
2012-09-26 13:25 ` George Dunlap
2012-09-26 14:29 ` Matthew Fioravante
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=20120926214343.GC4407@type \
--to=samuel.thibault@ens-lyon.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=matthew.fioravante@jhuapl.edu \
--cc=xen-devel@lists.xensource.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
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.