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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131004162808.GA10315@obsidianresearch.com>
Date:	Fri, 4 Oct 2013 10:28:08 -0600
From:	Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To:	Peter H?we <PeterHuewe@....de>
Cc:	tpmdd-devel@...ts.sourceforge.net,
	Ashley Lai <ashley@...leylai.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: TPM.ko module rename (was tpm: Pull everything related to
 /dev/tpmX into tpm-dev.c)

On Fri, Oct 04, 2013 at 05:50:01PM +0200, Peter H?we wrote:

> I'm not 100% sure what's the usual procedure for module renames, especially 
> since this is visible in userspace.
> 
> For users the easiest way would be to rename tpm.c to tpm-core.c and
> leave the module name as it is.  In git that's just a simple rename
> operation.

I agree, keeping the old name seems much safer.

I'm thinking of following the pattern seen in RTC. Rename tpm.c to
tpm-interface.c and eventually migrate all the driver model support
items into tpm-class.c.

Does that seem good? I'll respin the patches and test modular rebuilds.

Jason
--
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