linux-kernel - RE: [PATCH 1/1] [tegra] Make syncpt routines accessible by drivers

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <643E69AA4436674C8F39DCC2C05F763816BD96CFB3@HQMAIL03.nvidia.com>
Date:	Mon, 14 Feb 2011 17:52:21 -0800
From:	Andrew Chew <AChew@...dia.com>
To:	'Erik Gilling' <konkers@...roid.com>
CC:	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ccross@...roid.com" <ccross@...roid.com>,
	"olof@...om.net" <olof@...om.net>
Subject: RE: [PATCH 1/1] [tegra] Make syncpt routines accessible by drivers

> > You're right about that global nvhost_syncpt pointer.  That 
> drives me nuts as well.  Nevertheless, I'm not sure I'm 
> knowledgeable enough to do the required work to do this the 
> "right" way.  As far as I know, nvhost is a guaranteed 
> singleton in practice (not in implementation), so while this 
> is ugly, it will work fine for existing projects.
> 
> If you feel uncomfortable making this change, I recommend you include
> the private header file the way the dc does.

Okay, I'll do it this way then.--
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/