Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: buildroot@buildroot.org
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: [Buildroot] [PATCH] package/sunxi-mali-utgard-driver: bump to version 2026-11-06
Date: Fri, 20 Nov 2026 19:30:29 +0100	[thread overview]
Message-ID: <20261120183029.238611-1-giulio.benetti@benettiengineering.com> (raw)

The sunxi-mali-utgard-driver at git version b47f74c9 is failing to
build with Linux 7.0+ due to Linux commits 590d356aa433 ("mm: update
shmem_[kernel]_file_*() functions to use vma_flags_t") and
52a9e9cd181f ("mm: rename zap_vma_ptes() to zap_special_vma_range()").

This new version fixes the issue and builds up to Linux 7.3.

Fixes:

    linux/mali_memory_cow.c:384:25: error: implicit declaration of function ‘zap_vma_ptes’ [-Wimplicit-function-declaration]
    linux/mali_memory_swap_alloc.c:85:91: error: incompatible type for argument 3 of ‘shmem_file_setup’

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
---
 package/sunxi-mali-utgard-driver/sunxi-mali-utgard-driver.hash | 2 +-
 package/sunxi-mali-utgard-driver/sunxi-mali-utgard-driver.mk   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/sunxi-mali-utgard-driver/sunxi-mali-utgard-driver.hash b/package/sunxi-mali-utgard-driver/sunxi-mali-utgard-driver.hash
index 0b5dc9c2f8..832a31bfcf 100644
--- a/package/sunxi-mali-utgard-driver/sunxi-mali-utgard-driver.hash
+++ b/package/sunxi-mali-utgard-driver/sunxi-mali-utgard-driver.hash
@@ -1,3 +1,3 @@
 # Locally calculated
-sha256  b0cf26625db13989be54844d3625e6918bee6d4ae6d054da161a2bf9e3665532  sunxi-mali-utgard-driver-b47f74c92fbcbdf175a16052d1b0ce8345efc6b2.tar.gz
+sha256  23f23dc5d0b8a76ad2bea82c090d133160e4bed01559b5bfbfd0dd4f36144138  sunxi-mali-utgard-driver-ed75438ef1f464f3e13a568c8c3708e68359dde8.tar.gz
 sha256  8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643  LICENSE
diff --git a/package/sunxi-mali-utgard-driver/sunxi-mali-utgard-driver.mk b/package/sunxi-mali-utgard-driver/sunxi-mali-utgard-driver.mk
index 38946aa1e4..25f7400c30 100644
--- a/package/sunxi-mali-utgard-driver/sunxi-mali-utgard-driver.mk
+++ b/package/sunxi-mali-utgard-driver/sunxi-mali-utgard-driver.mk
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-SUNXI_MALI_UTGARD_DRIVER_VERSION = b47f74c92fbcbdf175a16052d1b0ce8345efc6b2
+SUNXI_MALI_UTGARD_DRIVER_VERSION = ed75438ef1f464f3e13a568c8c3708e68359dde8
 SUNXI_MALI_UTGARD_DRIVER_SITE = $(call github,benetti-engineering,sunxi-mali,$(SUNXI_MALI_UTGARD_DRIVER_VERSION))
 SUNXI_MALI_UTGARD_DRIVER_DEPENDENCIES = linux
 SUNXI_MALI_UTGARD_DRIVER_LICENSE = GPL-2.0
-- 
2.47.3

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2026-11-20 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 18:30 Giulio Benetti [this message]
2026-11-21 10:30 ` [Buildroot] [PATCH] package/sunxi-mali-utgard-driver: bump to version 2026-11-06 Peter Korsgaard

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=20261120183029.238611-1-giulio.benetti@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=buildroot@buildroot.org \
    /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