From 108de81a9ef6bc889d300626e7ff981c62c9644c Mon Sep 17 00:00:00 2001 From: Ben Dooks Date: Tue, 22 Sep 2009 16:46:11 -0700 Subject: [PATCH] --- yaml --- r: 164790 b: refs/heads/master c: 9ed7ef526ade622cdc22ac365a95197ddd1e09fb h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/spi/spi-summary | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 9c3be7822763..19db323e554f 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 5b61a749e8fd0a45a5e37c267d20a43ef0590d68 +refs/heads/master: 9ed7ef526ade622cdc22ac365a95197ddd1e09fb diff --git a/trunk/Documentation/spi/spi-summary b/trunk/Documentation/spi/spi-summary index 4a02d2508bc8..deab51ddc33e 100644 --- a/trunk/Documentation/spi/spi-summary +++ b/trunk/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).