Signed-off-by: Sebastian Siewior <[email protected]>
---
drivers/dma/dmaengine.c | 6 +++---
include/linux/dmaengine.h | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/dma/dmaengine.c b/drivers/dma/dmaengine.c
index 2996523..1299d43 100644
--- a/drivers/dma/dmaengine.c
+++ b/drivers/dma/dmaengine.c
@@ -42,9 +42,9 @@
*
* Each device has a kref, which is initialized to 1 when the device is
* registered. A kref_get is done for each device registered. When the
- * device is released, the coresponding kref_put is done in the release
+ * device is released, the corresponding kref_put is done in the release
* method. Every time one of the device's channels is allocated to a client,
- * a kref_get occurs. When the channel is freed, the coresponding kref_put
+ * a kref_get occurs. When the channel is freed, the corresponding kref_put
* happens. The device's release function does a completion, so
* unregister_device does a remove event, device_unregister, a kref_put
* for the first reference, then waits on the completion for all other
@@ -53,7 +53,7 @@
* Each channel has an open-coded implementation of Rusty Russell's "bigref,"
* with a kref and a per_cpu local_t. A dma_chan_get is called when a client
* signals that it wants to use a channel, and dma_chan_put is called when
- * a channel is removed or a client using it is unregesitered. A client can
+ * a channel is removed or a client using it is unregistered. A client can
* take extra references per outstanding transaction, as is the case with
* the NET DMA client. The release function does a kref_put on the device.
* -ChrisL, DanW
diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
index 261e43a..8b2481f 100644
--- a/include/linux/dmaengine.h
+++ b/include/linux/dmaengine.h
@@ -398,7 +398,7 @@ static inline enum dma_status dma_async_is_tx_complete(struct dma_chan *chan,
* @last_used: last cookie value handed out
*
* dma_async_is_complete() is used in dma_async_memcpy_complete()
- * the test logic is seperated for lightweight testing of multiple cookies
+ * the test logic is separated for lightweight testing of multiple cookies
*/
static inline enum dma_status dma_async_is_complete(dma_cookie_t cookie,
dma_cookie_t last_complete, dma_cookie_t last_used)
--
1.5.4.3
> ---------- Original message ----------
> From: Sebastian Siewior <[email protected]>
> Date: Mar 11, 2008 10:44 AM
> Subject: [PATCH] [DMA ENGINE] typo fixes
> To: Jesper Juhl <[email protected]>
> Cc: [email protected]
>
>
> Signed-off-by: Sebastian Siewior <[email protected]>
> ---
> drivers/dma/dmaengine.c | 6 +++---
> include/linux/dmaengine.h | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/dma/dmaengine.c b/drivers/dma/dmaengine.c
> index 2996523..1299d43 100644
> --- a/drivers/dma/dmaengine.c
> +++ b/drivers/dma/dmaengine.c
> @@ -42,9 +42,9 @@
> *
> * Each device has a kref, which is initialized to 1 when the device
is
> * registered. A kref_get is done for each device registered. When
the
> - * device is released, the coresponding kref_put is done in the
release
> + * device is released, the corresponding kref_put is done in the
release
> * method. Every time one of the device's channels is allocated to a
client,
> - * a kref_get occurs. When the channel is freed, the coresponding
kref_put
> + * a kref_get occurs. When the channel is freed, the corresponding
kref_put
> * happens. The device's release function does a completion, so
> * unregister_device does a remove event, device_unregister, a
kref_put
> * for the first reference, then waits on the completion for all other
> @@ -53,7 +53,7 @@
> * Each channel has an open-coded implementation of Rusty Russell's
"bigref,"
> * with a kref and a per_cpu local_t. A dma_chan_get is called when a
client
> * signals that it wants to use a channel, and dma_chan_put is called
when
> - * a channel is removed or a client using it is unregesitered. A
client can
> + * a channel is removed or a client using it is unregistered. A
client can
> * take extra references per outstanding transaction, as is the case
with
> * the NET DMA client. The release function does a kref_put on the
device.
> * -ChrisL, DanW
> diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
> index 261e43a..8b2481f 100644
> --- a/include/linux/dmaengine.h
> +++ b/include/linux/dmaengine.h
> @@ -398,7 +398,7 @@ static inline enum dma_status
> dma_async_is_tx_complete(struct dma_chan *chan,
> * @last_used: last cookie value handed out
> *
> * dma_async_is_complete() is used in dma_async_memcpy_complete()
> - * the test logic is seperated for lightweight testing of multiple
cookies
> + * the test logic is separated for lightweight testing of multiple
cookies
> */
> static inline enum dma_status dma_async_is_complete(dma_cookie_t
cookie,
> dma_cookie_t last_complete, dma_cookie_t
last_used)
> --
> 1.5.4.3
Acked-by: Maciej Sosnowski <[email protected]>
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
z siedziba w Gdansku
ul. Slowackiego 173
80-298 Gdansk
Sad Rejonowy Gdansk Polnoc w Gdansku,
VII Wydzial Gospodarczy Krajowego Rejestru Sadowego,
numer KRS 101882
NIP 957-07-52-316
Kapital zakladowy 200.000 zl
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.