Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) client-ip=2620:137:e000::3:6;
MIME-Version: 1.0
References: <20231213093044.2fc89781@canb.auug.org.au>
In-Reply-To: <20231213093044.2fc89781@canb.auug.org.au>
From:   Joel Stanley <joel@jms.id.au>
Date:   Thu, 14 Dec 2023 08:36:15 +1030
Message-ID: <CACPK8XevBYm8q1rHm4CyyqaNb3gAcksJUUh4QcOWMx_Um++8jA@mail.gmail.com>
Subject: Re: linux-next: build failure after merge of the aspeed tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Peter Yin <peteryin.openbmc@gmail.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, 13 Dec 2023 at 09:00, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the aspeed tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> make[4]: *** No rule to make target 'arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dtb', needed by 'arch/arm/boot/dts/aspeed/'.  Stop.
>
> Caused by commit
>
>   70fe22dd623e ("ARM: dts: aspeed: Harma: Add Meta Harma (AST2600) BMC")
>
> I have used the aspeed tree from next-20231212 for today.

Should be fixed today, sorry about that.

Cheers,

Joel