Since I'm actively maintaining the tpm subsystem for a few months now,
it's time to step up and be an official maintainer for the tpm subsystem,
atleast until I hear something different from my company.
The maintaining is done solely in my private time, out of private interest.
Speaking only on behalf of myself, trying to be as vendor neutral as possible.
Signed-off-by: Peter Huewe <[email protected]>
---
MAINTAINERS | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4fde706..936adb4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8475,6 +8475,7 @@ F: drivers/media/usb/tm6000/
TPM DEVICE DRIVER
M: Leonidas Da Silva Barbosa <[email protected]>
M: Ashley Lai <[email protected]>
+M: Peter Huewe <[email protected]>
M: Rajiv Andrade <[email protected]>
W: http://tpmdd.sourceforge.net
M: Marcel Selhorst <[email protected]>
--
1.7.5.4
On 10/22/2013 12:36 PM, Peter Huewe wrote:
> Since I'm actively maintaining the tpm subsystem for a few months now,
> it's time to step up and be an official maintainer for the tpm subsystem,
> atleast until I hear something different from my company.
>
> The maintaining is done solely in my private time, out of private interest.
> Speaking only on behalf of myself, trying to be as vendor neutral as possible.
>
> Signed-off-by: Peter Huewe <[email protected]>
> ---
> MAINTAINERS | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4fde706..936adb4 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8475,6 +8475,7 @@ F: drivers/media/usb/tm6000/
> TPM DEVICE DRIVER
> M: Leonidas Da Silva Barbosa <[email protected]>
> M: Ashley Lai <[email protected]>
> +M: Peter Huewe <[email protected]>
> M: Rajiv Andrade <[email protected]>
> W: http://tpmdd.sourceforge.net
> M: Marcel Selhorst <[email protected]>
>
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.
Hi Joel,
> Gesendet: Dienstag, 22. Oktober 2013 um 19:55 Uhr
> Von: "Joel Schopp" <[email protected]>
> 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
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" <[email protected]>
>
> > 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
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 <[email protected]> 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" <[email protected]>
>>
>> > 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
>> 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.
FYI I'm one of the two people who took over co-maintaining TrouSerS
after Kent stepped down. I am also reviewing tpm device driver patches
that go by, but I am glad others more knowledgeable about those drivers
such as you are there to be the maintainers. Thanks for stepping up.
On Tue, Oct 22, 2013 at 07:36:50PM +0200, Peter Huewe wrote:
> Since I'm actively maintaining the tpm subsystem for a few months now,
> it's time to step up and be an official maintainer for the tpm subsystem,
> atleast until I hear something different from my company.
Sounds good!
As others have said, please purge the list of inactive people...
Thanks,
Jason
Hi everyone,
Long time, no see..
I stopped being active (administrative-wise specially) since I handed
it over to Kent. Now that he stepped down, I can come back at my own
private time.
Peter, thank you a ton for stepping in. Since you're of course the
owner (yes, we need such figure), let me know if my help is desirable
or if you think there isn't additional bandwidth needed to maintain
it.
Cheers,
On Tue, Oct 22, 2013 at 6:52 PM, Jason Gunthorpe
<[email protected]> wrote:
> On Tue, Oct 22, 2013 at 07:36:50PM +0200, Peter Huewe wrote:
>> Since I'm actively maintaining the tpm subsystem for a few months now,
>> it's time to step up and be an official maintainer for the tpm subsystem,
>> atleast until I hear something different from my company.
>
> Sounds good!
>
> As others have said, please purge the list of inactive people...
>
> Thanks,
> Jason
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Hi Rajiv,
> Long time, no see..
Good to see you again.
> Peter, thank you a ton for stepping in.
> Since you're of course the owner (yes, we need such figure),
> let me know if my help is desirable or if you think there isn't
> additional bandwidth needed to maintain it.
Thanks for the offer - I think I can handle the maintenance effort itself,
HOWEVER I would really like to see you sticking around here as a reviewer,
due to your experience,
especially for the stuff I'm submitting.
The more reviewers the merrier ;)
Whether you want to be listed in MAINTAINERS or the subscription to tpmdd is enough is up to you.
Please tell me what you think, then I'd clean up the MAINTAINERS entry for the tpm subsystem ;)
Thanks,
Peter
On Thu, Oct 24, 2013 at 01:10:28AM +0200, Peter Huewe wrote:
> Thanks for the offer - I think I can handle the maintenance effort
> itself, HOWEVER I would really like to see you sticking around here
> as a reviewer, due to your experience, especially for the stuff I'm
> submitting.
Agreed, there are still lots of patches to go before the subsystem
meets the current kernel standard..
Speaking of which, has anyone looked at the rest of my series?? Shall
I repost it?
Thanks,
Jason
> Agreed, there are still lots of patches to go before the subsystem
> meets the current kernel standard..
>
> Speaking of which, has anyone looked at the rest of my series?? Shall
> I repost it?
Jason,
Are you referring to the for-tpm branch on github?
https://github.com/jgunthorpe/linux/commits/for-tpm
Peter already submitted most of the patches to James from this branch.
Let us know which series need to be review.
Thanks,
--Ashley Lai
On Wed, Oct 23, 2013 at 11:01:19PM -0500, Ashley Lai wrote:
>
> > Agreed, there are still lots of patches to go before the subsystem
> > meets the current kernel standard..
> >
> > Speaking of which, has anyone looked at the rest of my series?? Shall
> > I repost it?
>
> Jason,
> Are you referring to the for-tpm branch on github?
> https://github.com/jgunthorpe/linux/commits/for-tpm
> Peter already submitted most of the patches to James from this branch.
> Let us know which series need to be review.
All of those patches in for-tpm have gone to James.
However, the original series I posted included 5 additional patches
that have received no comment, available on:
https://github.com/jgunthorpe/linux/commits/tpm-devel
Jason Gunthorpe:
tpm: Pull everything related to /dev/tpmX into tpm-dev.c
tpm: Pull everything related to sysfs into tpm-sysfs.c
tpm: Create a tpm_class_ops structure and use it in the drivers
tpm: Use the ops structure instead of a copy in tpm_vendor_specific
tpm: Make tpm-dev allocate a per-file structure
These would have been posted as patch numbers 8 through 13 in the
original series.
I think what happened is at this point in the series module compile
broke. That is fixed now in the for-james pull, so the rest of the
series should be looked at.
Peter's checkpatch clean up will create some minor conflicts, so I
should probably resend the lot after rebasing it.
Jason
<snip>
> These would have been posted as patch numbers 8 through 13 in the
> original series.
>
> I think what happened is at this point in the series module compile
> broke. That is fixed now in the for-james pull, so the rest of the
> series should be looked at.
>
> Peter's checkpatch clean up will create some minor conflicts, so I
> should probably resend the lot after rebasing it.
>
If you rebase and resend I will commit to reviewing them.
Hi Jason,
> > Speaking of which, has anyone looked at the rest of my series?? Shall
> > I repost it?
> Jason Gunthorpe:
> tpm: Pull everything related to /dev/tpmX into tpm-dev.c
> tpm: Pull everything related to sysfs into tpm-sysfs.c
> tpm: Create a tpm_class_ops structure and use it in the drivers
> tpm: Use the ops structure instead of a copy in tpm_vendor_specific
> tpm: Make tpm-dev allocate a per-file structure
> Peter's checkpatch clean up will create some minor conflicts, so I
> should probably resend the lot after rebasing it.
Yeah that would be nice.
I did have a look at them, but not as close as I wanted to, yet ;(
Since they are making some major changes to the tpm subsystem I did not want to hurry them in for 3.12, but give them a rather good testing on my machines as well. (I know you did test them ;)
Unfortunately due to a lot of traveling that was not possible for me.
So please repost them, so we can make them ready for 3.13.
Thanks,
Peter
Hey Peter,
Yes, a cleanup there is way welcome. Please remove my name indeed, as
it doesn't make sense at this point, the lists should suffice.
I'll keep looking at the patches and try to review them for sure.
Cheers and thanks again for stepping in.
On Wed, Oct 23, 2013 at 9:10 PM, Peter Huewe <[email protected]> wrote:
> Hi Rajiv,
>> Long time, no see..
> Good to see you again.
>
>> Peter, thank you a ton for stepping in.
>> Since you're of course the owner (yes, we need such figure),
>> let me know if my help is desirable or if you think there isn't
>> additional bandwidth needed to maintain it.
>
> Thanks for the offer - I think I can handle the maintenance effort itself,
> HOWEVER I would really like to see you sticking around here as a reviewer,
> due to your experience,
> especially for the stuff I'm submitting.
>
> The more reviewers the merrier ;)
>
> Whether you want to be listed in MAINTAINERS or the subscription to tpmdd is enough is up to you.
> Please tell me what you think, then I'd clean up the MAINTAINERS entry for the tpm subsystem ;)
>
> Thanks,
> Peter