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] Fix linux build under sid and trixie
Date: Fri, 27 Sep 2024 19:18:27 +0200	[thread overview]
Message-ID: <54f8aa6d-10d3-41b3-84bd-7111aef77f9c@siemens.com> (raw)
In-Reply-To: <8241287c797aff79f4cbd359e6d2f72b8f12debd.camel@ilbers.de>

On 27.09.24 18:32, Uladzimir Bely wrote:
> On Fri, 2024-09-27 at 15:14 +0200, Jan Kiszka wrote:
>> On 27.09.24 08:36, Uladzimir Bely wrote:
>>> The patch for kernel is taken from the upstream where it
>>> was applied since linux-6.8.
>>
>> This does not make any sense. Update the stable version.
>>
>> Jan
>>
> 
> Hello.
> 
> Actually, build fails only for starfive target that uses non-mainline
> custom linux repo not haveing a branch with linux >= 6.7.
> 
> I think, the patch is worth applying at least for linux-starfive_6.6-
> visionfive2.bb.
> 
> Other targets are using bookworm at most, so for could leave them as is
> for now.
> 
> What do you think?

Just update the starfive kernel to its latest 6.6 revision.

Jan

-- 
Siemens AG, Technology
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 on the web visit https://groups.google.com/d/msgid/isar-users/54f8aa6d-10d3-41b3-84bd-7111aef77f9c%40siemens.com.

      reply	other threads:[~2024-09-27 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27  6:36 Uladzimir Bely
2024-09-27 13:14 ` 'Jan Kiszka' via isar-users
2024-09-27 16:32   ` Uladzimir Bely
2024-09-27 17:18     ` 'Jan Kiszka' via isar-users [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=54f8aa6d-10d3-41b3-84bd-7111aef77f9c@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