Subject: linux-next: build failure after merge of the regulator tree

From: Stephen Rothwell <[email-masked]>
Date: Mon, 8 Sep 2014 18:33:50 +1000

Hi all,

After merging the regulator tree, today's linux-next build (powerpc
allyesconfig) failed like this:

drivers/regulator/rk808-regulator.c:312:18: warning: 'struct rk808_board' declared inside parameter list
           struct rk808_board *pdata)
                  ^
drivers/regulator/rk808-regulator.c:312:18: warning: its scope is only this definition or declaration, which is probably not what you want
drivers/regulator/rk808-regulator.c: In function 'rk808_regulator_dts':
drivers/regulator/rk808-regulator.c:340:8: error: dereferencing pointer to incomplete type
   pdata->rk808_init_data[i] = rk808_reg_matches[i].init_data;
        ^
drivers/regulator/rk808-regulator.c:341:8: error: dereferencing pointer to incomplete type
   pdata->of_node[i] = rk808_reg_matches[i].of_node;
        ^
drivers/regulator/rk808-regulator.c: In function 'rk808_regulator_probe':
drivers/regulator/rk808-regulator.c:359:43: error: dereferencing pointer to incomplete type
   pdata = devm_kzalloc(&pdev->dev, sizeof(*pdata), GFP_KERNEL);
                                           ^
drivers/regulator/rk808-regulator.c:364:8: warning: passing argument 2 of 'rk808_regulator_dts' from incompatible pointer type
  ret = rk808_regulator_dts(client, pdata);
        ^
drivers/regulator/rk808-regulator.c:311:12: note: expected 'struct rk808_board *' but argument is of type 'struct rk808_board *'
 static int rk808_regulator_dts(struct i2c_client *client,
            ^
drivers/regulator/rk808-regulator.c:370:19: error: dereferencing pointer to incomplete type
   reg_data = pdata->rk808_init_data[i];
                   ^
drivers/regulator/rk808-regulator.c:379:26: error: dereferencing pointer to incomplete type
    config.of_node = pdata->of_node[i];
                          ^

Caused by commit 2cd64ae3d57b ("regulator: RK808: Add regulator driver
for RK808").

I have reverted that commit and all the following ones in the regulator
tree that touch this file.

-- 
Cheers,
Stephen Rothwell                    [email-masked]