The patch titled
spi-add-spi-over-gpio-driver-v3
has been added to the -mm tree. Its filename is
spi-add-spi-over-gpio-driver-v3.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: spi-add-spi-over-gpio-driver-v3
From: Michael Buesch <mb@xxxxxxxxx>
Simple spelling fixes since v2.
Signed-off-by: Michael Buesch <mb@xxxxxxxxx>
Cc: David Brownell <david-b@xxxxxxxxxxx>
Cc: Pierre Ossman <drzeus-list@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
MAINTAINERS | 10 +++++-----
drivers/spi/Kconfig | 2 +-
include/linux/spi/spi_gpio.h | 12 +++++++++---
3 files changed, 15 insertions(+), 9 deletions(-)
diff -puN MAINTAINERS~spi-add-spi-over-gpio-driver-v3 MAINTAINERS
--- a/MAINTAINERS~spi-add-spi-over-gpio-driver-v3
+++ a/MAINTAINERS
@@ -3876,11 +3876,6 @@ M: dbrownell@xxxxxxxxxxxxxxxxxxxxx
L: spi-devel-general@xxxxxxxxxxxxxxxxxxxxx
S: Maintained
-SPI GPIO MASTER DRIVER
-P: Michael Buesch
-M: mb@xxxxxxxxx
-S: Maintained
-
SPU FILE SYSTEM
P: Jeremy Kerr
M: jk@xxxxxxxxxx
@@ -3889,6 +3884,11 @@ L: cbe-oss-dev@xxxxxxxxxx
W: http://www.ibm.com/developerworks/power/cell/
S: Supported
+SPI GPIO MASTER DRIVER
+P: Michael Buesch
+M: mb@xxxxxxxxx
+S: Maintained
+
STABLE BRANCH:
P: Greg Kroah-Hartman
M: greg@xxxxxxxxx
diff -puN drivers/spi/Kconfig~spi-add-spi-over-gpio-driver-v3 drivers/spi/Kconfig
--- a/drivers/spi/Kconfig~spi-add-spi-over-gpio-driver-v3
+++ a/drivers/spi/Kconfig
@@ -107,7 +107,7 @@ config SPI_GPIO
help
This is a platform driver that can be used for bitbanging
an SPI bus over GPIO pins.
- Select this, if you have any SPI device that is connected via
+ Select this if you have any SPI device that is connected via
GPIO pins.
The module will be called spi_gpio.
diff -puN include/linux/spi/spi_gpio.h~spi-add-spi-over-gpio-driver-v3 include/linux/spi/spi_gpio.h
--- a/include/linux/spi/spi_gpio.h~spi-add-spi-over-gpio-driver-v3
+++ a/include/linux/spi/spi_gpio.h
@@ -15,7 +15,9 @@
#include <linux/spi/spi.h>
-/** struct spi_gpio_platform_data - Data definitions for a SPI-GPIO device.
+/**
+ * struct spi_gpio_platform_data - Data definitions for a SPI-GPIO device.
+ *
* This structure holds information about a GPIO-based SPI device.
*
* @pin_clk: The GPIO pin number of the CLOCK pin.
@@ -51,13 +53,17 @@ struct spi_gpio_platform_data {
void *boardinfo_setup_data;
};
-/** SPI_GPIO_PLATDEV_NAME - The platform device name string.
+/**
+ * SPI_GPIO_PLATDEV_NAME - The platform device name string.
+ *
* The name string that has to be used for platform_device_alloc
* when allocating a spi-gpio device.
*/
#define SPI_GPIO_PLATDEV_NAME "spi-gpio"
-/** spi_gpio_next_id - Get another platform device ID number.
+/**
+ * spi_gpio_next_id - Get another platform device ID number.
+ *
* This returns the next platform device ID number that has to be used
* for platform_device_alloc. The ID is opaque and should not be used for
* anything else.
_
Patches currently in -mm which might be from mb@xxxxxxxxx are
origin.patch
linux-next.patch
gpio-sysfs-interface-updated-gpio-linux-next-fixes-for-sysfs-support.patch
gpio-add-bt8xxgpio-driver.patch
gpio-add-bt8xxgpio-driver-checkpatch-fixes.patch
gpio-add-bt8xxgpio-driver-checkpatch-fixes-fix.patch
gpio-add-bt8xxgpio-driver-checkpatch-fixes-cleanup.patch
gpiolib-allow-user-selection.patch
gpiolib-allow-user-selection-update.patch
spi-add-spi-over-gpio-driver.patch
spi-add-spi-over-gpio-driver-v3.patch
mmc-add-gpio-based-mmc-sd-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
