linux-kernel - Re: [PATCH 2/3] x86, pci sta2x11-fixup: add function to access sta2x11 instance id

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]

Date:	Fri, 8 Mar 2013 16:13:34 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Davide Ciminaghi <ciminaghi@...dd.com>
Cc:	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	x86@...nel.org, rubini@...dd.com, sameo@...ux.intel.com,
	giancarlo.asnaghi@...com, mturquette@...aro.org,
	linus.walleij@...aro.org, rob.herring@...xeda.com,
	broonie@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] x86, pci sta2x11-fixup: add function to access sta2x11 instance id

On Friday 08 March 2013, Davide Ciminaghi wrote:
> 
> The sta2x11 instance id will be included in clock names to make them
> unique in case of multiple sta2x11's living on the same machine.
> 
> Signed-off-by: Davide Ciminaghi <ciminaghi@...dd.com>

I might be missing something, but this seems counterintuitive. Shouldn't
the clock names really be constant and independent of the instance?

The instance should be identified already by the dev_name, right?

	Arnd
--
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/