mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Alexandre TORGUE <alexandre.torgue@foss.st.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Alexandre Torgue <alexandre.torgue@st.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the stm32 tree
Date: Thu, 6 Jun 2024 13:14:37 +0200	[thread overview]
Message-ID: <5770f01f-2341-4fed-81da-3803f3c54f03@denx.de> (raw)
In-Reply-To: <361a9191-c320-411e-a628-ff41298391a9@foss.st.com>

On 6/6/24 8:54 AM, Alexandre TORGUE wrote:
> Hi

Hello everyone,

> On 6/6/24 01:29, Marek Vasut wrote:
>> On 6/6/24 1:12 AM, Stephen Rothwell wrote:
>>> Hi all,
>>
>> Hello everyone,
>>
>>> After merging the stm32 tree, today's linux-next build (arm
>>> multi_v7_defconfig) failed like this:
>>>
>>> make[4]: *** No rule to make target 
>>> 'arch/arm/boot/dts/st/stm32mp135f-dhsom-dhsbc.dtb', needed by 
>>> 'arch/arm/boot/dts/st/dtbs-list'.  Stop.
>>>
>>> Caused by commit
>>>
>>>    12ff8e167641 ("ARM: dts: stm32: Add support for STM32MP13xx DHCOR 
>>> SoM and DHSBC board")
>>>
>>> I have used the stm32 tree from next-20240605 for today.
>>
>> Fixed in
>>
>> [PATCH] ARM: dts: stm32: Fix STM32MP13xx DHCOR DHSBC Makefile entry
>>
>> sent to linux-arm-kernel .
>>
>> Thanks for the report, sorry for the breakage.
> 
> 
> My fault, I tested to build the board using
> "make  st/stm32mp135f-dhcor-dhsbc.dtb"

That's what I also use most of the time, and OE does its own DT builds.
The LKP bot did find it today.

> Fixed in stm32-next by applying Marek patch. I'll maybe squash it with 
> initial patch for my PR.

Thanks !

      reply	other threads:[~2024-06-06 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 23:12 Stephen Rothwell
2024-06-05 23:29 ` Marek Vasut
2024-06-06  6:54   ` Alexandre TORGUE
2024-06-06 11:14     ` Marek Vasut [this message]

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=5770f01f-2341-4fed-81da-3803f3c54f03@denx.de \
    --to=marex@denx.de \
    --cc=alexandre.torgue@foss.st.com \
    --cc=alexandre.torgue@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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

all inboxes | Powered by JetHome®