summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorBen Dooks <ben@simtec.co.uk>2009-09-22 16:46:11 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2009-09-23 07:39:44 -0700
commit9ed7ef526ade622cdc22ac365a95197ddd1e09fb (patch)
tree241a76fa472b1363d6857ad41aec7ed89789355b /Documentation
parent5b61a749e8fd0a45a5e37c267d20a43ef0590d68 (diff)
downloadop-kernel-dev-9ed7ef526ade622cdc22ac365a95197ddd1e09fb.zip
op-kernel-dev-9ed7ef526ade622cdc22ac365a95197ddd1e09fb.tar.gz
spi: fix spelling of `automatically' in documentation
Fix spelling of `automatically' in Documentation/spi/spi-summary. Signed-off-by: Ben Dooks <ben@simtec.co.uk> Cc: David Brownell <david-b@pacbell.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/spi/spi-summary2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/spi/spi-summary b/Documentation/spi/spi-summary
index 4a02d25..deab51d 100644
--- a/Documentation/spi/spi-summary
+++ b/Documentation/spi/spi-summary
@@ -350,7 +350,7 @@ SPI protocol drivers somewhat resemble platform device drivers:
.resume = CHIP_resume,
};
-The driver core will autmatically attempt to bind this driver to any SPI
+The driver core will automatically attempt to bind this driver to any SPI
device whose board_info gave a modalias of "CHIP". Your probe() code
might look like this unless you're creating a device which is managing
a bus (appearing under /sys/class/spi_master).
OpenPOWER on IntegriCloud