summaryrefslogtreecommitdiff
path: root/target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2015-09-11 16:32:00 +0000
committerFelix Fietkau <nbd@openwrt.org>2015-09-11 16:32:00 +0000
commit0b5d87fd30d3d8edd27cbcc9b7688b1f9d740b2e (patch)
tree633627a1e4d5761b609c7ff1682b69ee85b06d9f /target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch
parent2ce833060a6ac412d0df362edb950b19da9af04c (diff)
downloadmtk-20170518-0b5d87fd30d3d8edd27cbcc9b7688b1f9d740b2e.zip
mtk-20170518-0b5d87fd30d3d8edd27cbcc9b7688b1f9d740b2e.tar.gz
mtk-20170518-0b5d87fd30d3d8edd27cbcc9b7688b1f9d740b2e.tar.bz2
brcm2708: update 4.1 patches
As usual, this patches were taken (and rebased) from https://github.com/raspberrypi/linux/commits/rpi-4.1.y Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> SVN-Revision: 46853
Diffstat (limited to 'target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch')
-rw-r--r--target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch4
1 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch b/target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch
index b4cedef..8f62474 100644
--- a/target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch
+++ b/target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch
@@ -1,7 +1,7 @@
-From 94b88ebdb90e6b3ae6eca18355a2ff318041318f Mon Sep 17 00:00:00 2001
+From 0e76c9361112e7a88d08b3bf3d23c6ba936de01e Mon Sep 17 00:00:00 2001
From: Gordon Hollingworth <gordon@fiveninjas.com>
Date: Tue, 23 Jun 2015 09:53:40 +0100
-Subject: [PATCH 080/148] Fix driver detection failure Check that the buffer
+Subject: [PATCH 080/171] Fix driver detection failure Check that the buffer
response is non-zero meaning the touchscreen was detected
---