linux-kernel - Re: [tpmdd-devel] [PATCH 07/13] tpm: Remove tpm_show_caps_1

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: <201310020038.32404.PeterHuewe@gmx.de>
Date:	Wed, 2 Oct 2013 00:38:31 +0200
From:	Peter Hüwe <PeterHuewe@....de>
To:	tpmdd-devel@...ts.sourceforge.net
Cc:	Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
	Leonidas Da Silva Barbosa <leosilva@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org, Rajiv Andrade <mail@...jiv.net>,
	Sirrix AG <tpmdd@...rix.com>
Subject: Re: [tpmdd-devel] [PATCH 07/13] tpm: Remove tpm_show_caps_1_2

Hi Jason,

Am Mittwoch, 2. Oktober 2013, 00:21:13 schrieb Jason Gunthorpe:
> On Wed, Oct 02, 2013 at 12:09:22AM +0200, Peter H?we wrote:
> >    Since the tpm_spi_stm_st33, tpm_i2c_nuvoton and tpm_i2c_atmel drivers
> >    are not yet merged and were heavily improved by you anyway, please
> >    include this improvement directly in the new drivers.
> 
> Okay, it is easy enough to invert the patch order and put the drivers
> last. I am not submitting the st33 driver, but when things are done I
> will send Mathias a patch with the changes from this series that are
> needed and he can deal with re-submitting his driver.
> 
> FWIW, I needed the drivers first to keep my world sane when testing
> this thing, so the patches are all as-tested from my perspective.

nevermind and don't worry - the way you submitted the patches is perfectly 
fine for me.
You can keep the patches seperate and in case of doubt I can simply squash 
them in the end.

Thanks,
Peter
--
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/