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]
Date:	Wed, 16 Jun 2010 14:06:38 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	grant.likely@...retlab.ca
Cc:	sparclinux@...r.kernel.org, sfr@...b.auug.org.au,
	devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] sparc/of: Move of_device fields into struct
 pdev_archdata

From: Grant Likely <grant.likely@...retlab.ca>
Date: Fri, 04 Jun 2010 15:11:33 -0600

> This patch moves SPARC architecture specific data members out of
> struct of_device and into the pdev_archdata structure.  The reason
> for this change is to unify the struct of_device definition amongst
> all the architectures.  It also remvoes the .sysdata, .slot, .portid
> and .clock_freq properties because they aren't actually used by
> anything.
> 
> A subsequent patch will replace struct of_device entirely with struct
> platform_device and the of_platform support code will share common
> routines with the platform bus (but the bus instances themselves can
> remain separate).
> 
> This patch also adds 'struct resources *resource' and num_resources
> to match the fields defined in struct platform_device.  After this
> change, 'struct platform_device' can be used as a drop-in replacement
> for 'struct of_platform'.
> 
> This change is in preparation for merging the of_platform_bus_type
> with the platform_bus_type.
> 
> Signed-off-by: Grant Likely <grant.likely@...retlab.ca>

Acked-by: David S. Miller <davem@...emloft.net>
--
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