From: Luigi Semenzato <semenzato@google.com>
To: Ashley D Lai <adlai@linux.vnet.ibm.com>
Cc: Peter Huewe <PeterHuewe@gmx.de>,
Da Silva Barbosa <leosilva@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, Sirrix AG <tpmdd@sirrix.com>,
Rajiv Andrade <mail@srajiv.net>,
tpmdd-devel@lists.sourceforge.net, Leonidas@google.com
Subject: Re: [tpmdd-devel] [PATCH] tpm: MAINTAINERS: Add myself as tpm maintainer
Date: Tue, 22 Oct 2013 12:48:58 -0700 [thread overview]
Message-ID: <CAA25o9SBX3busjmO5aRFiawEW6mtADEfyuz3ebthF5gcC_qzCQ@mail.gmail.com> (raw)
In-Reply-To: <1382470976.3742.7.camel@buffalo>
I know how to reach Rajiv. Let me ping him. (I am not copying him
here for privacy.)
On Tue, Oct 22, 2013 at 12:42 PM, Ashley D Lai <adlai@linux.vnet.ibm.com> wrote:
> On Tue, 2013-10-22 at 21:33 +0200, Peter Huewe wrote:
>> Hi Joel,
>>
>> > Gesendet: Dienstag, 22. Oktober 2013 um 19:55 Uhr
>> > Von: "Joel Schopp" <jschopp@linux.vnet.ibm.com>
>>
>> > I have no objection to you adding yourself here. I do think we should
>> > probably also cut the list down at the same time as I don't think all
>> > the listed maintainers are active anymore. Also, the list is getting a
>> > bit unwieldy. If everyone maintains it nobody maintains it.
>>
>> I agree with you here, this was also the reason I took it over when Kent stepped down and noone else stepped in of the current maintainers, leaving the subsystem more or less unmaintained.
>>
>> About the removing the other maintainers:
>> I already thought about that too and contacted the "maintainers" -
>> I got a response back from Ashley (as its part of her job to look after the subsystem) and Marcel, stating that they are atleast looking at the patches.
>> No response from Rajiv, Leonidas or Sirrix :(
>>
>>
>> Thanks,
>> Peter
>>
>
> Rajiv has moved on to a different company. Haven't heard from him for a
> while.
>
> --Ashley Lai
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> tpmdd-devel mailing list
> tpmdd-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
next prev parent reply other threads:[~2013-10-22 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 17:36 [PATCH] tpm: MAINTAINERS: Add myself as tpm maintainer Peter Huewe
2013-10-22 17:55 ` [tpmdd-devel] " Joel Schopp
2013-10-22 19:33 ` Aw: " Peter Huewe
2013-10-22 19:42 ` Ashley D Lai
2013-10-22 19:48 ` Luigi Semenzato [this message]
2013-10-22 19:59 ` Joel Schopp
2013-10-22 20:52 ` Jason Gunthorpe
2013-10-23 19:41 ` Rajiv Andrade
2013-10-23 23:10 ` Aw: " Peter Huewe
2013-10-24 3:27 ` Jason Gunthorpe
2013-10-24 4:01 ` Ashley Lai
2013-10-24 4:16 ` Jason Gunthorpe
2013-10-24 4:28 ` Joel Schopp
2013-10-24 7:46 ` Aw: " Peter Huewe
2013-10-29 1:36 ` Rajiv Andrade
2013-10-22 19:58 Leonidas Da Silva Barbosa
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=CAA25o9SBX3busjmO5aRFiawEW6mtADEfyuz3ebthF5gcC_qzCQ@mail.gmail.com \
--to=semenzato@google.com \
--cc=Leonidas@google.com \
--cc=PeterHuewe@gmx.de \
--cc=adlai@linux.vnet.ibm.com \
--cc=leosilva@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@srajiv.net \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@sirrix.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 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).