Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1571251 > unrolled thread

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

Started byStephen Rothwell <sfr@canb.auug.org.au>
First post2017-02-01 03:50 +0100
Last post2017-02-03 12:40 +0100
Articles 4 — 2 participants

Back to article view | Back to linux.kernel


Contents

  linux-next: build failure after merge of the regulator tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-02-01 03:50 +0100
    Re: linux-next: build failure after merge of the regulator tree Mark Brown <broonie@kernel.org> - 2017-02-01 11:10 +0100
      Re: linux-next: build failure after merge of the regulator tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-02-02 23:40 +0100
        Re: linux-next: build failure after merge of the regulator tree Mark Brown <broonie@kernel.org> - 2017-02-03 12:40 +0100

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

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2017-02-01 03:50 +0100
Subjectlinux-next: build failure after merge of the regulator tree
Message-ID<t5T9D-5K-5@gated-at.bofh.it>
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

[toc] | [next] | [standalone]


#1571416

FromMark Brown <broonie@kernel.org>
Date2017-02-01 11:10 +0100
Message-ID<t601r-4A9-3@gated-at.bofh.it>
In reply to#1571251

[Multipart message — attachments visible in raw view] — view raw

On Wed, Feb 01, 2017 at 01:42:21PM +1100, Stephen Rothwell wrote:

> 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.

Discarded that commit.

[toc] | [prev] | [next] | [standalone]


#1572777

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2017-02-02 23:40 +0100
Message-ID<t6ycO-1zz-9@gated-at.bofh.it>
In reply to#1571416
Hi Mark,

On Wed, 1 Feb 2017 10:03:43 +0000 Mark Brown <broonie@kernel.org> wrote:
>
> On Wed, Feb 01, 2017 at 01:42:21PM +1100, Stephen Rothwell wrote:
> 
> > 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.  
> 
> Discarded that commit.

The patch is still there ...

-- 
Cheers,
Stephen Rothwell

[toc] | [prev] | [next] | [standalone]


#1573039

FromMark Brown <broonie@kernel.org>
Date2017-02-03 12:40 +0100
Message-ID<t6KnE-10D-11@gated-at.bofh.it>
In reply to#1572777

[Multipart message — attachments visible in raw view] — view raw

On Fri, Feb 03, 2017 at 09:30:04AM +1100, Stephen Rothwell wrote:

> > Discarded that commit.

> The patch is still there ...

Only in the merge branch, it got dropped from the source branch but the
merge ended up not being rebuilt.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web