lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4D4036CB.2090200@linux.vnet.ibm.com>
Date:	Wed, 26 Jan 2011 12:59:23 -0200
From:	Rajiv Andrade <srajiv@...ux.vnet.ibm.com>
To:	James Morris <jmorris@...ei.org>
CC:	Olof Johansson <olof@...om.net>, linux-kernel@...r.kernel.org,
	Debora Velarde <debora@...ux.vnet.ibm.com>,
	Marcel Selhorst <m.selhorst@...rix.com>,
	tpmdd-devel@...ts.sourceforge.net, Matthew Garrett <mjg@...hat.com>
Subject: Re: [PATCH] tpm: fix panic caused by "tpm: Autodetect itpm devices"

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@...ux.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ