From: Rajiv Andrade <srajiv@linux.vnet.ibm.com>
To: James Morris <jmorris@namei.org>
Cc: Olof Johansson <olof@lixom.net>,
linux-kernel@vger.kernel.org,
Debora Velarde <debora@linux.vnet.ibm.com>,
Marcel Selhorst <m.selhorst@sirrix.com>,
tpmdd-devel@lists.sourceforge.net,
Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH] tpm: fix panic caused by "tpm: Autodetect itpm devices"
Date: Wed, 26 Jan 2011 12:59:23 -0200 [thread overview]
Message-ID: <4D4036CB.2090200@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1101211002490.13919@tundra.namei.org>
On 01/20/2011 09:11 PM, James Morris wrote:
> On Thu, 20 Jan 2011, Rajiv Andrade wrote:
>
>> On 01/20/2011 03:37 PM, Olof Johansson wrote:
>>> Are all TPM maintainers MIA? This is a trivial patch that fixes a
>>> panic, and it was a late-added regression in 2.6.37.
>>>
>> Not myself. I missed this one unfortunately in my work queue, sorry, will keep
>> alert to avoid this happening again.
>>
>> Acked-by: Rajiv Andrade<srajiv@linux.vnet.ibm.com>
> Rajiv,
>
> I've mentioned this at least once before: as maintainer of TPM, ideally,
> what you should be doing is collecting the TPM patches, testing them in
> your own tree, then pushing them to me with an indication of where they
> need to end up (e.g. bugfixes for current linus vs. next), preferably via
> git.
>
> This is a significant part of what distinguishes maintainership from
> simply developing or reviewing code.
>
>
> - James
Sorry for the delays, I'm setting up a git tree now. Thanks for the
heads up.
Rajiv
next prev parent reply other threads:[~2011-01-26 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 3:24 [PATCH] tpm: fix panic caused by "tpm: Autodetect itpm devices" Olof Johansson
2011-01-20 17:37 ` Olof Johansson
2011-01-20 18:44 ` Rajiv Andrade
2011-01-20 23:11 ` James Morris
2011-01-26 14:59 ` Rajiv Andrade [this message]
2011-01-24 0:31 ` James Morris
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=4D4036CB.2090200@linux.vnet.ibm.com \
--to=srajiv@linux.vnet.ibm.com \
--cc=debora@linux.vnet.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.selhorst@sirrix.com \
--cc=mjg@redhat.com \
--cc=olof@lixom.net \
--cc=tpmdd-devel@lists.sourceforge.net \
/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.