From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751283AbdBACmZ (ORCPT ); Tue, 31 Jan 2017 21:42:25 -0500 Received: from ozlabs.org ([103.22.144.67]:47633 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751180AbdBACmY (ORCPT ); Tue, 31 Jan 2017 21:42:24 -0500 Date: Wed, 1 Feb 2017 13:42:21 +1100 From: Stephen Rothwell To: Mark Brown , Liam Girdwood Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Bhumika Goyal Subject: linux-next: build failure after merge of the regulator tree Message-ID: <20170201134221.7a413d9b@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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