[PATCH 1/7] OF: make drivers depend on CONFIG_OF instead ofCONFIG_PPC_OF

[Grant Likely]

On Tue, Nov 16, 2010 at 5:07 PM, Stephen Neuendorffer
<stephen.neuendorffer at xilinx.com> wrote:
>
>
>> -----Original Message-----
>> From:
> devicetree-discuss-bounces+stephen.neuendorffer=xilinx.com at lists.ozlabs.
> org [mailto:devicetree-
>> discuss-bounces+stephen.neuendorffer=xilinx.com at lists.ozlabs.org] On
> Behalf Of Stephen Rothwell
>> Sent: Tuesday, November 16, 2010 4:00 PM
>> To: Rob Herring
>> Cc: devicetree-discuss at lists.ozlabs.org; Rob Herring
>> Subject: Re: [PATCH 1/7] OF: make drivers depend on CONFIG_OF instead
> ofCONFIG_PPC_OF
>>
>> Hi Mitch,
>>
>> On Tue, 16 Nov 2010 13:40:58 -0700 Grant Likely
> <grant.likely at secretlab.ca> wrote:
>> >
>> > On Tue, Nov 16, 2010 at 02:33:49PM -0600, Rob Herring wrote:
>> > > From: Rob Herring <rob.herring at calxeda.com>
>> > >
>> > > Some OF drivers could likely be used on non-powerpc OF based
> platforms,
>> > > so fix the kconfig depends to be CONFIG_OF instead of
> CONFIG_PPC_OF
>> > >
>> > > Signed-off-by: Rob Herring <rob.herring at calxeda.com>
>> >
>> > Which of these drivers are you actually using, or going to use in
> the
>> > near future?
>>
>> And have you made sure that you haven't broken the allmodconfig builds
> on
>> other architectures that enable CONFIG_OF?
>
> In general, is there an easy way to do this?  I can easily see a
> difficult to bound testing
> problem here, that might benefit from a build farm.

I can put it in my experimental branch that gets picked up by the
build server that ozlabs maintains.  However, having some level of
sanity checking beforehand is important before I do so.  Including a
log of what testing has been performed in the patch description is
always the right thing to do.

g.