public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the broadcom tree
Date: Tue, 28 Jun 2022 10:07:05 +1000	[thread overview]
Message-ID: <20220628100705.449df135@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 582 bytes --]

Hi all,

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

drivers/soc/bcm/bcm2835-power.c: In function 'bcm2835_power_probe':
drivers/soc/bcm/bcm2835-power.c:643:31: error: 'struct bcm2835_pm' has no member named 'rpivid_asb'
  643 |         power->rpivid_asb = pm->rpivid_asb;
      |                               ^~

Caused by commit

  d5eba4a03b1d ("soc: bcm: bcm2835-power: Add support for BCM2711's RPiVid ASB")

I have used the broadcom tree from next-20220627 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-06-28  0:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28  0:07 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-03  2:20 linux-next: build failure after merge of the broadcom tree Stephen Rothwell
2025-06-05  3:06 ` Florian Fainelli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220628100705.449df135@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=stefan.wahren@i2se.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox