aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm2708/patches-4.19/950-0380-overlays-Fix-multiple-instantiation-of-sc16is7xx.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-0380-overlays-Fix-multiple-instantiation-of-sc16is7xx.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-0380-overlays-Fix-multiple-instantiation-of-sc16is7xx.patch')
-rw-r--r--target/linux/brcm2708/patches-4.19/950-0380-overlays-Fix-multiple-instantiation-of-sc16is7xx.patch4
1 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/brcm2708/patches-4.19/950-0380-overlays-Fix-multiple-instantiation-of-sc16is7xx.patch b/target/linux/brcm2708/patches-4.19/950-0380-overlays-Fix-multiple-instantiation-of-sc16is7xx.patch
index feda48228a..95455d7cc7 100644
--- a/target/linux/brcm2708/patches-4.19/950-0380-overlays-Fix-multiple-instantiation-of-sc16is7xx.patch
+++ b/target/linux/brcm2708/patches-4.19/950-0380-overlays-Fix-multiple-instantiation-of-sc16is7xx.patch
@@ -1,7 +1,7 @@
-From 238fd7a2cda959e7c645b7a6fc4967049c12f69f Mon Sep 17 00:00:00 2001
+From 649efe5db3900ed3bbfd3c3daa3b96d8fc0b9d68 Mon Sep 17 00:00:00 2001
From: Phil Elwell <phil@raspberrypi.org>
Date: Fri, 22 Mar 2019 16:44:47 +0000
-Subject: [PATCH 380/782] overlays: Fix multiple-instantiation of sc16is7xx*
+Subject: [PATCH 380/806] overlays: Fix multiple-instantiation of sc16is7xx*
The registration of the fixed clocks uses the node name as the clock
name, causing a clash if two clock nodes have the same name, regardless