linux-kernel - Re: [PATCH v4 1/3] AM35x: Using OMAP3 generic hwmods

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:	Thu, 22 Sep 2011 13:10:19 -0600 (MDT)
From:	Paul Walmsley <paul@...an.com>
To:	Abhilash K V <abhilash.kv@...com>
cc:	linux-omap@...r.kernel.org, "Maupin, Chase" <chase.maupin@...com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	tony@...mide.com, linux@....linux.org.uk, b-cousson@...com,
	aneesh@...com, khilman@...com, santosh.shilimkar@...com,
	christian.gmeiner@...il.com
Subject: Re: [PATCH v4 1/3] AM35x: Using OMAP3 generic hwmods

+ Chase

Hi

On Thu, 22 Sep 2011, Abhilash K V wrote:

> This patch enables AM35x SoCs to use generic OMAP3 hwmods
> (i,e. omap3xxx_hwmods) by allowing am35xx_init_early() to
> disable the modules which are not present in AM3517.
> 
> Reviewed-by: Sanjeev Premi <premi@...com>
> Signed-off-by: Abhilash K V <abhilash.kv@...com>

We now use a different approach for registering hwmods that are 
device-specific.  Could you please take a look at the approach that's in 
Tony's master branch and use it instead to handle AM3517 hwmod 
registration?

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