linux-kernel - Re: [V2 PATCH 00/10] of: Consolidate scattered device node pointers in struct device

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <fa686aa41003180835k5af2d0e4o11f8ab9ca2e905ed@mail.gmail.com>
Date:	Thu, 18 Mar 2010 09:35:30 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	davem@...emloft.net, benh@...nel.crashing.org,
	linux-kernel@...r.kernel.org, michal.simek@...alogix.com,
	linuxppc-dev@...ts.ozlabs.org, sparclinux@...r.kernel.org,
	microblaze-uclinux@...e.uq.edu.au
Subject: Re: [V2 PATCH 00/10] of: Consolidate scattered device node pointers 
	in struct device

On Thu, Mar 18, 2010 at 9:22 AM, Grant Likely <grant.likely@...retlab.ca> wrote:
> Currently, each of_device has a copy of the device tree node pointer in both
> .node, and in .dev.archdata.of_node (microblaze and powerpc) or
> .dev.archdata.prom_node (sparc).  Also, other architectures will be adding
> CONFIG_OF support, and they will also need a reference to the device tree
> node pointer from struct device.
>
> This series consolidates the device node pointer by adding .of_node to
> struct device (conditional on CONFIG_OF) and removing the archdata.of_node,
> archdata.prom_node and of_device.node users.  The pointer is moved out of
> dev_archdata and into struct device proper so that of_node doesn't need to
> get manually added to archdata for each architecture that enables CONFIG_OF.

This series is also available in my git tree:

git://git.secretlab.ca/git/linux-2.6 experimental-devicetree
--
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/