The patch titled
gpio calls don't need i/o barriers
has been removed from the -mm tree. Its filename was
gpio-calls-dont-need-i-o-barriers.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: gpio calls don't need i/o barriers
From: David Brownell <david-b@xxxxxxxxxxx>
Clarify that drivers using the GPIO operations don't need to issue io
barrier instructions themselves. Previously this wasn't clear, and at
least one platform assumed otherwise (and would thus break various
otherwise-portable drivers which don't issue barriers).
Signed-off-by: David Brownell <dbrownell@xxxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/gpio.txt | 3 +++
1 file changed, 3 insertions(+)
diff -puN Documentation/gpio.txt~gpio-calls-dont-need-i-o-barriers Documentation/gpio.txt
--- a/Documentation/gpio.txt~gpio-calls-dont-need-i-o-barriers
+++ a/Documentation/gpio.txt
@@ -75,6 +75,9 @@ using the include file:
If you stick to this convention then it'll be easier for other developers to
see what your code is doing, and help maintain it.
+Note that these operations include I/O barriers on platforms which need to
+use them; drivers don't need to add them explicitly.
+
Identifying GPIOs
-----------------
_
Patches currently in -mm which might be from david-b@xxxxxxxxxxx are
origin.patch
git-leds.patch
git-mmc.patch
git-mtd.patch
git-backlight.patch
acpi-add-acpi_pm_device_sleep_state-helper-routine.patch
drivers-pmc-msp71xx-gpio-char-driver.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
