public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] linux-starfive: Fix build with GNU make 4.4
Date: Fri, 11 Apr 2025 01:55:44 +0300	[thread overview]
Message-ID: <eeff8bae4b8f097b1780161df649f0b410019d15.camel@ilbers.de> (raw)
In-Reply-To: <e955e591-8225-4010-95f5-e7bbbf24b5d3@siemens.com>

On Thu, 2025-04-10 at 15:07 +0200, Jan Kiszka wrote:
> 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

Sorry for missleading, but JH7110_VisionFive2_devel actually doesn't
include the fix. I tried to update to the recent branch and there is
still error.

So, we still need the patch (I appeared to take it from "pinetabv-
6.6.y-devel" branch, not from "our" upstream).

The only benefit from moving to 6.12 could be the fact that it already
includes another patch we are applying.

So, for now I would leave patch 2 as is.

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

-- 
Best regards,
Uladzimir.

-- 
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/eeff8bae4b8f097b1780161df649f0b410019d15.camel%40ilbers.de.

  reply	other threads:[~2025-04-10 22:55 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
2025-04-10 22:55         ` Uladzimir Bely [this message]
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=eeff8bae4b8f097b1780161df649f0b410019d15.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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