On Mon, Jun 28, 2010 at 7:38 PM, Stephen Rothwell [off-list ref] wr=
ote:

Hi Stephen,

On Mon, 28 Jun 2010 10:57:33 -0700 Stephen Neuendorffer <stephen.neuendor=

ffer@xilinx.com> wrote:

quoted

2) config OF is currently implemented in the architecture code. =A0This
should be non-architecture dependent and selected by the arches that
need it.

Comments greatly appreciated, in particular if you have
likely-to-be-easy-to-get-accepted suggestions for 3), or feel like
carefully solving 2) in
a way which doesn't bork the existing of-based arches.

See the following patch set. =A0Parts 1, 2 and 3 could be applied to the
respective architecture trees as well as Grant's tree to aleviate some
conflict problems. =A0Part 5 could wait until a later time if necessary.
However, this is relatively trivial, so we could just collect ACKs and
put it all in Grant's tree and live with any minor pain.

Having OF in more than one Kconfig file should not cause any problems as
long as they are all the same.

I've got an Ack from David now.  I'll wait for more acks, and then
pull the whole series of 5 into my devicetree-next branch.  It's
certainly less invasive that some of the other changes arch changes
I've taken through my tree.

g.