From: Vinod Koul <vinod.koul@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Jonathan Corbet <corbet@lwn.net>,
Jiri Kosina <trivial@kernel.org>,
linux-doc@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH trivial] DMA-API: Spelling s/This/Think/
Date: Fri, 22 May 2015 17:59:53 +0530 [thread overview]
Message-ID: <20150522122953.GX3140@localhost> (raw)
In-Reply-To: <1432209427-20233-1-git-send-email-geert+renesas@glider.be>
On Thu, May 21, 2015 at 01:57:07PM +0200, Geert Uytterhoeven wrote:
> Also remove spaces before TABs while we're at it.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Looks good to me, but the question si which tree does this go thru..
--
~Vinod
> ---
> Documentation/DMA-API-HOWTO.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/DMA-API-HOWTO.txt b/Documentation/DMA-API-HOWTO.txt
> index 0f7afb2bb442e07f..16b6f9509cb65b62 100644
> --- a/Documentation/DMA-API-HOWTO.txt
> +++ b/Documentation/DMA-API-HOWTO.txt
> @@ -240,7 +240,7 @@ the case would look like this:
>
> if (!dma_set_mask_and_coherent(dev, DMA_BIT_MASK(64))) {
> using_dac = 1;
> - consistent_using_dac = 1;
> + consistent_using_dac = 1;
> } else if (!dma_set_mask_and_coherent(dev, DMA_BIT_MASK(32))) {
> using_dac = 0;
> consistent_using_dac = 0;
> @@ -353,7 +353,7 @@ There are two types of DMA mappings:
> transfer, unmapped right after it (unless you use dma_sync_* below)
> and for which hardware can optimize for sequential accesses.
>
> - This of "streaming" as "asynchronous" or "outside the coherency
> + Think of "streaming" as "asynchronous" or "outside the coherency
> domain".
>
> Good examples of what to use streaming mappings for are:
> --
> 1.9.1
>
--
next prev parent reply other threads:[~2015-05-22 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 11:57 [PATCH trivial] DMA-API: Spelling s/This/Think/ Geert Uytterhoeven
2015-05-22 12:29 ` Vinod Koul [this message]
2015-05-22 12:55 ` Geert Uytterhoeven
2015-05-22 13:16 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150522122953.GX3140@localhost \
--to=vinod.koul@intel.com \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox