aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm2708/patches-4.19/950-0486-staging-mmal-vchiq-Fix-memory-leak-in-error-path.patch
diff options
context:
space:
mode:
authorÁlvaro Fernández Rojas <noltari@gmail.com>2019-09-19 16:43:19 +0200
committerÁlvaro Fernández Rojas <noltari@gmail.com>2019-09-19 17:38:18 +0200
commit4f8b350be0b90554c93908458a27be34e8b722ca (patch)
tree8b39d985a590db8cc4eb275d68496cfa212d5ede /target/linux/brcm2708/patches-4.19/950-0486-staging-mmal-vchiq-Fix-memory-leak-in-error-path.patch
parentb400179ca66647944a26f4d4b7b4fd53a3d2f0d1 (diff)
downloadupstream-4f8b350be0b90554c93908458a27be34e8b722ca.tar.gz
upstream-4f8b350be0b90554c93908458a27be34e8b722ca.tar.bz2
upstream-4f8b350be0b90554c93908458a27be34e8b722ca.zip
brcm2708: update to latest patches from RPi foundation
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Diffstat (limited to 'target/linux/brcm2708/patches-4.19/950-0486-staging-mmal-vchiq-Fix-memory-leak-in-error-path.patch')
-rw-r--r--target/linux/brcm2708/patches-4.19/950-0486-staging-mmal-vchiq-Fix-memory-leak-in-error-path.patch4
1 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/brcm2708/patches-4.19/950-0486-staging-mmal-vchiq-Fix-memory-leak-in-error-path.patch b/target/linux/brcm2708/patches-4.19/950-0486-staging-mmal-vchiq-Fix-memory-leak-in-error-path.patch
index 740921f84e..d973c56985 100644
--- a/target/linux/brcm2708/patches-4.19/950-0486-staging-mmal-vchiq-Fix-memory-leak-in-error-path.patch
+++ b/target/linux/brcm2708/patches-4.19/950-0486-staging-mmal-vchiq-Fix-memory-leak-in-error-path.patch
@@ -1,7 +1,7 @@
-From 12f6eaa7d1f747d8df369bead3ce3d7b8b965801 Mon Sep 17 00:00:00 2001
+From 250db0df9643d122e00313313102c642f1adac72 Mon Sep 17 00:00:00 2001
From: Dave Stevenson <dave.stevenson@raspberrypi.org>
Date: Thu, 2 May 2019 15:50:01 +0100
-Subject: [PATCH 486/782] staging: mmal-vchiq: Fix memory leak in error path
+Subject: [PATCH 486/806] staging: mmal-vchiq: Fix memory leak in error path
On error, vchiq_mmal_component_init could leave the
event context allocated for ports.