[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100311.102043.40590962.davem@davemloft.net>
Date: Thu, 11 Mar 2010 10:20:43 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: grant.likely@...retlab.ca
Cc: monstr@...str.eu, gregkh@...e.de, benh@...nel.crashing.org,
akpm@...ux-foundation.org, sfr@...b.auug.org.au, jgarzik@...ox.com,
ben-linux@...ff.org, dwmw2@...radead.org,
jeremy.kerr@...onical.com, James.Bottomley@...e.de,
broonie@...nsource.wolfsonmicro.com,
microblaze-uclinux@...e.uq.edu.au, linux-kernel@...r.kernel.org,
linuxppc-dev@...abs.org, sparclinux@...r.kernel.org,
linux-ide@...r.kernel.org, netdev@...r.kernel.org,
linux-i2c@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
linux-scsi@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH 00/37] OF: move device node pointer into struct device.
From: Grant Likely <grant.likely@...retlab.ca>
Date: Thu, 11 Mar 2010 11:03:47 -0700
> Currently on OF enabled platforms, the device node pointer is stored in
> both device.archdata.of_node (.prom_node on sparc), and in of_device.node
> OF device tree support is being generalized to work on any platform, so
> instead of adding the of_node pointer to each platform's archdata
> individually, this patch series moves the of_node pointer into struct
> device proper and fixes up all users to reference the new location.
>
> The last 3 patches in this series remove the old .archdata.of_node,
> .archdata.prom_node and of_device.node instances.
>
> This series has been compile tested on powerpc, sparc and microblaze,
> (allmodconfig used on sparc and powerpc) and boot tested on an mpc5200
> powerpc. All known (or at least all I could find) in-tree users of the
> old names have been removed.
Three or four of the patches don't apply because only your tree
has those "/* temporary */" comments, f.e. in arch/sparc/kernel/pci.c
I took care of this when applying to my tree.
> This series should also be fully bisectable. After I collect acks, I
> would like to get this whole series into linux-next to see if I've
> missed any references, but I can probably hold off merging the last
> three patches when the 2.6.35 merge window opens to give out of tree
> users a bit more time to adapt. In fact, I'd probably wait a few
> extra days after pushing out the bulk of this series before I push the
> last 3 patches into my linux-next branch to isolate the drivers that I
> missed while fixing.
I'd rather you just apply the sparc one immediately in 2.6.35 and
not wait at all.
--
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