diff options
author | Paolo Ornati <ornati@fastwebnet.it> | 2006-10-03 16:57:56 -0400 |
---|---|---|
committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 16:57:56 -0400 |
commit | 670e9f34ee3c7e052514c85014d2fdd99b672cdc (patch) | |
tree | 41f82a763ba6d5ca2fcb84d6a05808d095d4d051 /Documentation/spi/spi-summary | |
parent | 53cb47268e6b38180d9f253527135e1c69c5d310 (diff) |
Documentation: remove duplicated words
Remove many duplicated words under Documentation/ and do other small
cleanups.
Examples:
"and and" --> "and"
"in in" --> "in"
"the the" --> "the"
"the the" --> "to the"
...
Signed-off-by: Paolo Ornati <ornati@fastwebnet.it>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/spi/spi-summary')
-rw-r--r-- | Documentation/spi/spi-summary | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/spi/spi-summary b/Documentation/spi/spi-summary index 068732d32276..72795796b13d 100644 --- a/Documentation/spi/spi-summary +++ b/Documentation/spi/spi-summary | |||
@@ -262,7 +262,7 @@ NON-STATIC CONFIGURATIONS | |||
262 | Developer boards often play by different rules than product boards, and one | 262 | Developer boards often play by different rules than product boards, and one |
263 | example is the potential need to hotplug SPI devices and/or controllers. | 263 | example is the potential need to hotplug SPI devices and/or controllers. |
264 | 264 | ||
265 | For those cases you might need to use use spi_busnum_to_master() to look | 265 | For those cases you might need to use spi_busnum_to_master() to look |
266 | up the spi bus master, and will likely need spi_new_device() to provide the | 266 | up the spi bus master, and will likely need spi_new_device() to provide the |
267 | board info based on the board that was hotplugged. Of course, you'd later | 267 | board info based on the board that was hotplugged. Of course, you'd later |
268 | call at least spi_unregister_device() when that board is removed. | 268 | call at least spi_unregister_device() when that board is removed. |
@@ -322,7 +322,7 @@ As soon as it enters probe(), the driver may issue I/O requests to | |||
322 | the SPI device using "struct spi_message". When remove() returns, | 322 | the SPI device using "struct spi_message". When remove() returns, |
323 | the driver guarantees that it won't submit any more such messages. | 323 | the driver guarantees that it won't submit any more such messages. |
324 | 324 | ||
325 | - An spi_message is a sequence of of protocol operations, executed | 325 | - An spi_message is a sequence of protocol operations, executed |
326 | as one atomic sequence. SPI driver controls include: | 326 | as one atomic sequence. SPI driver controls include: |
327 | 327 | ||
328 | + when bidirectional reads and writes start ... by how its | 328 | + when bidirectional reads and writes start ... by how its |