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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

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

drivers/regulator/anatop-regulator.c: In function 'anatop_regulator_probe':
drivers/regulator/anatop-regulator.c:310:24: error: assignment of member 'enable' in read-only object
    anatop_rops.enable  = regulator_enable_regmap;
                        ^
drivers/regulator/anatop-regulator.c:311:24: error: assignment of member 'disable' in read-only object
    anatop_rops.disable = regulator_disable_regmap;
                        ^
drivers/regulator/anatop-regulator.c:312:27: error: assignment of member 'is_enabled' in read-only object
    anatop_rops.is_enabled = regulator_is_enabled_regmap;
                           ^

Caused by commit

  524d339a9d6b ("regulator: anatop-regulator: constify regulator_ops structure")

I can only assume that this patch has been rebased since it was tested.

I have used the regulator tree from next-20170131 for today.

-- 
Cheers,
Stephen Rothwell
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux