public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] linux-starfive: Fix build with GNU make 4.4
Date: Thu, 10 Apr 2025 15:07:30 +0200	[thread overview]
Message-ID: <e955e591-8225-4010-95f5-e7bbbf24b5d3@siemens.com> (raw)
In-Reply-To: <b77b8c919c94a03162da16ec1172ada5ad5d48f0.camel@ilbers.de>

On 10.04.25 09:25, Uladzimir Bely wrote:
> On Wed, 2025-04-09 at 16:09 +0200, Jan Kiszka wrote:
>> On 08.04.25 13:33, Uladzimir Bely wrote:
>>> After updating "make" in trixie, kernel build fails with errors
>>> like:
>>>
>>> ```
>>> make[10]: *** .NOTINTERMEDIATE and .SECONDARY are mutually
>>> exclusive.  Stop.
>>> make[9]: *** [../scripts/Makefile.build:480:
>>> drivers/gpu/drm/img/img-rogue] Error 2
>>> make[9]: *** Waiting for unfinished jobs....
>>> ```
>>>
>>> Branch "JH7110_VisionFive2_devel" we are using doesn't include
>>> the fix, so we are not updating SRC_REV here, just taking
>>> the patch from branch "JH7110_VIsionFive2_6.12.y_devel.
>>
>> And why aren't you switching to the newer kernel directly?
>>
>> Jan
> 
> These patches are aimed to fix CI build issues, while switching to new
> kernel require testing with hardware since I don't have firm confidence
> that they will work out of the box.
> 

That's not the point. You will test the result anyway, won't you?

We should not pile up patches in isar for upstream if upstream has them
in newer versions. That isar is not a BSP layer. This here is for demo
and testing purposes.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/e955e591-8225-4010-95f5-e7bbbf24b5d3%40siemens.com.

  reply	other threads:[~2025-04-10 13:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 11:33 [PATCH 0/2] Fix riscv64/trixie build Uladzimir Bely
2025-04-08 11:33 ` [PATCH 1/2] u-boot-starfive-visionfive2: Fix build with swig 4.3.0 Uladzimir Bely
2025-04-09 14:06   ` 'Jan Kiszka' via isar-users
2025-04-10 22:51     ` Uladzimir Bely
2025-04-11  8:11       ` 'Jan Kiszka' via isar-users
2025-04-11 10:13         ` Uladzimir Bely
2025-04-11 13:35           ` 'Jan Kiszka' via isar-users
2025-04-08 11:33 ` [PATCH 2/2] linux-starfive: Fix build with GNU make 4.4 Uladzimir Bely
2025-04-09 14:09   ` 'Jan Kiszka' via isar-users
2025-04-10  7:25     ` Uladzimir Bely
2025-04-10 13:07       ` 'Jan Kiszka' via isar-users [this message]
2025-04-10 22:55         ` Uladzimir Bely
2025-04-11  9:50           ` 'Jan Kiszka' via isar-users

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=e955e591-8225-4010-95f5-e7bbbf24b5d3@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=ubely@ilbers.de \
    /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