diff options
| author | John Crispin <john@openwrt.org> | 2016-03-08 18:11:49 +0000 |
|---|---|---|
| committer | John Crispin <john@openwrt.org> | 2016-03-08 18:11:49 +0000 |
| commit | cd2114e19ceffb17b0f093718334148859f1adac (patch) | |
| tree | 62158040bf861945a26eafea53f100f9db69b202 /target/linux/brcm2708/patches-4.4/0152-bcm2835-sdhost-Restore-ATOMIC-flag-to-PIO-sg-mapping.patch | |
| parent | 7099b6c416c511fb943d2f32ef7daf8abcda858c (diff) | |
| download | upstream-cd2114e19ceffb17b0f093718334148859f1adac.tar.gz upstream-cd2114e19ceffb17b0f093718334148859f1adac.tar.bz2 upstream-cd2114e19ceffb17b0f093718334148859f1adac.zip | |
brcm2708: update linux 4.4 patches to latest version
As usual these patches were extracted from the raspberry pi repo:
https://github.com/raspberrypi/linux/tree/rpi-4.4.y
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
SVN-Revision: 48966
Diffstat (limited to 'target/linux/brcm2708/patches-4.4/0152-bcm2835-sdhost-Restore-ATOMIC-flag-to-PIO-sg-mapping.patch')
| -rw-r--r-- | target/linux/brcm2708/patches-4.4/0152-bcm2835-sdhost-Restore-ATOMIC-flag-to-PIO-sg-mapping.patch | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/brcm2708/patches-4.4/0152-bcm2835-sdhost-Restore-ATOMIC-flag-to-PIO-sg-mapping.patch b/target/linux/brcm2708/patches-4.4/0152-bcm2835-sdhost-Restore-ATOMIC-flag-to-PIO-sg-mapping.patch index a7fbc443d4..48aca151dc 100644 --- a/target/linux/brcm2708/patches-4.4/0152-bcm2835-sdhost-Restore-ATOMIC-flag-to-PIO-sg-mapping.patch +++ b/target/linux/brcm2708/patches-4.4/0152-bcm2835-sdhost-Restore-ATOMIC-flag-to-PIO-sg-mapping.patch @@ -1,7 +1,7 @@ -From 8e6120c43831dc99923873d061c88355cc9bd7a2 Mon Sep 17 00:00:00 2001 +From f395ff998f2bde846499b1a0ef84519989dc2d4e Mon Sep 17 00:00:00 2001 From: Phil Elwell <phil@raspberrypi.org> Date: Mon, 15 Feb 2016 10:00:27 +0000 -Subject: [PATCH 152/156] bcm2835-sdhost: Restore ATOMIC flag to PIO sg mapping +Subject: [PATCH 152/170] bcm2835-sdhost: Restore ATOMIC flag to PIO sg mapping Allocation problems have been seen in a wireless driver, and this is the only change which might have been responsible. |