1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/spi/spi-summary b/Documentation/spi/spi-summary
index deab51ddc33e..4884cb33845d 100644
--- a/Documentation/spi/spi-summary
+++ b/Documentation/spi/spi-summary
@@ -538,7 +538,7 @@ SPI MESSAGE QUEUE
 The bulk of the driver will be managing the I/O queue fed by transfer().
 That queue could be purely conceptual.  For example, a driver used only
-for low-frequency sensor acess might be fine using synchronous PIO.
+for low-frequency sensor access might be fine using synchronous PIO.
 But the queue will probably be very real, using message->queue, PIO,
 often DMA (especially if the root filesystem is in SPI flash), and

diff --git a/Documentation/spi/spi-summary b/Documentation/spi/spi-summary index deab51ddc33e..4884cb33845d 100644 --- a/Documentation/spi/spi-summary +++ b/Documentation/spi/spi-summary
@@ -538,7 +538,7 @@ SPI MESSAGE QUEUE
538	The bulk of the driver will be managing the I/O queue fed by transfer().	538	The bulk of the driver will be managing the I/O queue fed by transfer().
539		539
540	That queue could be purely conceptual. For example, a driver used only	540	That queue could be purely conceptual. For example, a driver used only
541	for low-frequency sensor acess might be fine using synchronous PIO.	541	for low-frequency sensor access might be fine using synchronous PIO.
542		542
543	But the queue will probably be very real, using message->queue, PIO,	543	But the queue will probably be very real, using message->queue, PIO,
544	often DMA (especially if the root filesystem is in SPI flash), and	544	often DMA (especially if the root filesystem is in SPI flash), and