linux-kernel - Re: [PATCH-V2] arm/dts: AM33XX: Set the default status of module to "disabled" state

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: <20120824200736.GX11011@atomide.com>
Date:	Fri, 24 Aug 2012 13:07:36 -0700
From:	Tony Lindgren <tony@...mide.com>
To:	Vaibhav Hiremath <hvaibhav@...com>
Cc:	devicetree-discuss@...ts.ozlabs.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linux-omap@...r.kernel.org, Benoit Cousson <b-cousson@...com>,
	Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH-V2] arm/dts: AM33XX: Set the default status of module
 to "disabled" state

* Vaibhav Hiremath <hvaibhav@...com> [120815 04:24]:
> Ideally in common SoC dtsi file should set all modules
> to "disabled" state and it should get enabled in respective
> EVM/Board dts file as per usage.
> 
> This patch sets default status of all modules to "disabled"
> state in am33xx.dtsi file. Currently there are no modules
> supported as part of Bone and EVM dts support, so care
> to add entry "status = "okay"" while adding support for any
> module.
> 
> Signed-off-by: Vaibhav Hiremath <hvaibhav@...com>
> Acked-by: Arnd Bergmann <arnd@...db.de>
> Cc: Benoit Cousson <b-cousson@...com>
> Cc: Grant Likely <grant.likely@...retlab.ca>
> Cc: Tony Lindgren <tony@...mide.com>
> ---
> Changes from V1:
> 	- Fixed indentation issue caused due to extra spaces.

Thanks applying into devel-dt branch.

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