From: Nathan Fontenot <nfont@austin.ibm.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@lists.ozlabs.org,
microblaze-uclinux@itee.uq.edu.au
Subject: Re: [RFC PATCH 2/5] Merge dynamic OF code to of_dynamic.c
Date: Thu, 05 Nov 2009 10:59:22 -0600 [thread overview]
Message-ID: <4AF3046A.4050508@austin.ibm.com> (raw)
In-Reply-To: <fa686aa40911042355l73c7511bod3b2f651e9c9a5a4@mail.gmail.com>
Grant Likely wrote:
> Hi Nathan,
>
> Thanks for the patches. Comments below.
>
> On Wed, Nov 4, 2009 at 3:16 PM, Nathan Fontenot <nfont@austin.ibm.com> wrote:
>> Creation of the OF dynamic device tree update code in drivers/of. This
>> merges the common device tree updating routines to add/remove nodes and
>> properties from powerpc and microblaze. All of the new code is conditional
>> based on a new OF_DYNAMIC config option.
>
> Rather than one patch to create all the moved functions, and then
> subsequent patches to remove the duplicates from each arch, I've been
> using the pattern of one patch for each function or couple of
> functions to both remove from the old files and add to the new home.
> Would you be able to do the same for your patches here? The merging
> is complicated enough without having to track changes to a function
> between separate commits. Moving one function at a time will also
> make bisecting more friendly.
>
Shouldn't be a problem.
> Also, have you checked what impact these changes have on SPARC?
>
I took a look at sparc code, but will do again as I redo the patches to
make there are no impacts.
>> --- linux-next.orig/drivers/of/Makefile 2009-11-03 11:18:08.000000000 -0600
>> +++ linux-next/drivers/of/Makefile 2009-11-03 13:42:35.000000000 -0600
>> @@ -1,6 +1,7 @@
>> obj-y = base.o
>> -obj-$(CONFIG_OF_DEVICE) += device.o platform.o
>> -obj-$(CONFIG_OF_GPIO) += gpio.o
>> -obj-$(CONFIG_OF_I2C) += of_i2c.o
>> -obj-$(CONFIG_OF_SPI) += of_spi.o
>> -obj-$(CONFIG_OF_MDIO) += of_mdio.o
>> +obj-$(CONFIG_OF_DEVICE) += device.o platform.o
>> +obj-$(CONFIG_OF_GPIO) += gpio.o
>> +obj-$(CONFIG_OF_I2C) += of_i2c.o
>> +obj-$(CONFIG_OF_SPI) += of_spi.o
>> +obj-$(CONFIG_OF_MDIO) += of_mdio.o
>> +obj-$(CONFIG_OF_DYNAMIC) += of_dynamic.o
>
> Unrelated whitespace churn makes it hard to see what actually changed.
>
ok.
-Nathan Fontenot
next prev parent reply other threads:[~2009-11-05 16:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 22:07 [RFC PATCH 0/5] Merge common dynamic OF device tree code Nathan Fontenot
2009-11-04 22:14 ` [RFC PATCH 1/5] Move devtree_lock and allnodes declaration to of.h Nathan Fontenot
2009-11-04 22:14 ` Nathan Fontenot
2009-11-04 22:16 ` [RFC PATCH 2/5] Merge dynamic OF code to of_dynamic.c Nathan Fontenot
2009-11-05 7:55 ` Grant Likely
2009-11-05 7:55 ` Grant Likely
2009-11-05 16:59 ` Nathan Fontenot [this message]
2009-11-04 22:18 ` [RFC PATCH 3/5] powerpc and pseries updates for new OF dynamic code Nathan Fontenot
2009-11-04 22:19 ` [RFC PATCH 4/5] Microblaze updates for " Nathan Fontenot
2009-11-04 22:19 ` Nathan Fontenot
2009-11-04 22:20 ` [RFC PATCH 5/5] powerpc/iseries updates for new " Nathan Fontenot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF3046A.4050508@austin.ibm.com \
--to=nfont@austin.ibm.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.