From vulab at iscas.ac.cn  Tue Dec  2 01:52:52 2025
From: vulab at iscas.ac.cn (Haotian Zhang)
Date: Tue,  2 Dec 2025 17:52:52 +0800
Subject: [PATCH] staging: vc04_services: vchiq_bus: Check return value of of_dma_configure()
Message-ID: <20251202095253.1640-1-vulab@iscas.ac.cn>

vchiq_device_register() ignores the return value of of_dma_configure(),
which may return -EPROBE_DEFER when the IOMMU is not ready or other error
codes. This allows device registration to proceed with incomplete DMA
configuration.

Check of_dma_configure() return value and fail device registration
on error.

Fixes: 027e5703de6b ("staging: vc04_services: vchiq_arm: Add new bus type and device type")
Signed-off-by: Haotian Zhang <vulab at iscas.ac.cn>
---
 .../staging/vc04_services/interface/vchiq_arm/vchiq_bus.c  | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_bus.c b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_bus.c
index 41ece91ab88a..8d920a7a3777 100644
--- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_bus.c
+++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_bus.c
@@ -80,7 +80,12 @@ vchiq_device_register(struct device *parent, const char *name)
 
 	device->drv_mgmt = dev_get_drvdata(parent);
 
-	of_dma_configure(&device->dev, parent->of_node, true);
+	ret = of_dma_configure(&device->dev, parent->of_node, true);
+	if (ret) {
+		dev_err(parent, "DMA configuration failed for %s: %d\n", name, ret);
+		kfree(device);
+		return NULL;
+	}
 
 	ret = device_register(&device->dev);
 	if (ret) {
-- 
2.50.1.windows.1



From dan.carpenter at linaro.org  Tue Dec  2 02:18:10 2025
From: dan.carpenter at linaro.org (Dan Carpenter)
Date: Tue, 2 Dec 2025 13:18:10 +0300
Subject: [PATCH] staging: vc04_services: vchiq_bus: Check return value of
 of_dma_configure()
In-Reply-To: <20251202095253.1640-1-vulab@iscas.ac.cn>
References: <20251202095253.1640-1-vulab@iscas.ac.cn>
Message-ID: <aS684lo6j3ldvrPn@stanley.mountain>

You're not working against the latest tree so this doesn't apply.

On Tue, Dec 02, 2025 at 05:52:52PM +0800, Haotian Zhang wrote:
> vchiq_device_register() ignores the return value of of_dma_configure(),
> which may return -EPROBE_DEFER when the IOMMU is not ready or other error
> codes. This allows device registration to proceed with incomplete DMA
> configuration.
> 

If of_dma_configure() returns -EPROBE_DEFER then this will just fail and
that's not really any better than the existing behavior...

regards,
dan carpenter

> Check of_dma_configure() return value and fail device registration
> on error.
> 
> Fixes: 027e5703de6b ("staging: vc04_services: vchiq_arm: Add new bus type and device type")
> Signed-off-by: Haotian Zhang <vulab at iscas.ac.cn>



From robh at kernel.org  Thu Dec 11 11:38:53 2025
From: robh at kernel.org (Rob Herring (Arm))
Date: Thu, 11 Dec 2025 13:38:53 -0600
Subject: [PATCH v2] arm64: broadcom: bcm2712: Drop rp1 overlay
Message-ID: <20251211193854.1778221-1-robh@kernel.org>

It's a requirement that DT overlays be applied at build time in order to
validate them as overlays are not validated on their own, but the
rp1.dtbo is not applied to anything. The rp1.dtso overlay doesn't work
on its own as there are additional settings needed as seen in
bcm2712-rpi-5-b.dts. In addition, the 'rp1_nexus' node is applied to the
wrong place in the DT as it should be under a PCIe root port rather than
the host bridge. There's also a duplicate overlay in drivers/misc/rp1/.

For these reasons, just drop the overlay to fix the warning until all
these issues can be fixed.

Signed-off-by: Rob Herring (Arm) <robh at kernel.org>
---
The missing applying of rp1.dtbo is now a warning in v6.19-rc1. This
should be sent to Linus ASAP.

v2:
 - Drop the overlay instead of trying to rework. The addition of
   ethernet0 alias complicates that.
---
 arch/arm64/boot/dts/broadcom/Makefile | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/arch/arm64/boot/dts/broadcom/Makefile b/arch/arm64/boot/dts/broadcom/Makefile
index 83d45afc6588..031875a277d7 100644
--- a/arch/arm64/boot/dts/broadcom/Makefile
+++ b/arch/arm64/boot/dts/broadcom/Makefile
@@ -14,8 +14,7 @@ dtb-$(CONFIG_ARCH_BCM2835) += bcm2711-rpi-400.dtb \
 			      bcm2837-rpi-3-b.dtb \
 			      bcm2837-rpi-3-b-plus.dtb \
 			      bcm2837-rpi-cm3-io3.dtb \
-			      bcm2837-rpi-zero-2-w.dtb \
-			      rp1.dtbo
+			      bcm2837-rpi-zero-2-w.dtb
 
 subdir-y	+= bcmbca
 subdir-y	+= northstar2
-- 
2.51.0



From tomasz.jaworski at torqly.pl  Thu Dec 18 00:41:00 2025
From: tomasz.jaworski at torqly.pl (Tomasz Jaworski)
Date: Thu, 18 Dec 2025 08:41:00 GMT
Subject: =?UTF-8?Q?Ulga_na_sk=C5=82adki_ZUS?=
Message-ID: <20251218084500-0.1.tu.d9ifj.0.no8gf5ej0t@torqly.pl>

Dzie? dobry, 

chcia?bym wskaza? Pa?stwu mo?liwo?? zarz?dzania benefitami w ?atwy spos?b, poprzez nasze intuicyjne narz?dzie, jakim jest karta lunchowa. 

Nasze karty oferuj? wygod?, oszcz?dno?ci i zdrowe wybory ?ywieniowe. Dofinansowanie posi?k?w jest korzystne dla obu stron. Karty lunch to dla pracodawcy realne oszcz?dno?ci w postaci zwolnienia z ZUS do 450 z? miesi?cznie na pracownika. 

Kart? mo?na do?adowa? dowoln? kwot?, a niewykorzystane ?rodki nie przepadaj?, lecz przechodz? na kolejny miesi?c. 

Mog? przedstawi? ofert?, kt?ra pozwoli zoptymalizowa? koszty i zapewni? pracownikom po??dany benefit?


Pozdrawiam
Tomasz Jaworski