From: Julia Lawall <julia.lawall@lip6.fr>
To: Tamara Diaconita <diaconitatamara@gmail.com>
Cc: corbet@lwn.net, outreachy-kernel@googlegroups.com,
linux-doc@vger.kernel.org,
Tamara Diaconita <diaconita.tamara@gmail.com>
Subject: Re: [Outreachy kernel] [PATCH] Documentation: Fix typos
Date: Wed, 15 Mar 2017 21:07:56 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703152107120.4005@hadrien> (raw)
In-Reply-To: <20170315175811.4187-1-diaconita.tamara@gmail.com>
On Wed, 15 Mar 2017, Tamara Diaconita wrote:
> Fix typos in sync_file.txt to make documentation grammatically correct.
It's a bit picky, but you are not making the text grammatically correct,
You are fixing spelling mistakes, but not changing any aspect of the
grammar.
julia
>
> Signed-off-by: Tamara Diaconita <diaconita.tamara@gmail.com>
> ---
> Documentation/sync_file.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/sync_file.txt b/Documentation/sync_file.txt
> index 269681a..c3d033a 100644
> --- a/Documentation/sync_file.txt
> +++ b/Documentation/sync_file.txt
> @@ -37,7 +37,7 @@ dma_fence_signal(), when it has finished using (or processing) that buffer.
> Out-fences are fences that the driver creates.
>
> On the other hand if the driver receives fence(s) through a sync_file from
> -userspace we call these fence(s) 'in-fences'. Receiveing in-fences means that
> +userspace we call these fence(s) 'in-fences'. Receiving in-fences means that
> we need to wait for the fence(s) to signal before using any buffer related to
> the in-fences.
>
> --
> 2.9.3
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20170315175811.4187-1-diaconita.tamara%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>
next prev parent reply other threads:[~2017-03-15 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 17:58 [PATCH] Documentation: Fix typos Tamara Diaconita
2017-03-15 20:07 ` Julia Lawall [this message]
2017-03-15 21:56 ` [Outreachy kernel] " Alison Schofield
2017-03-15 21:57 ` Julia Lawall
2017-03-15 22:10 ` 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=alpine.DEB.2.20.1703152107120.4005@hadrien \
--to=julia.lawall@lip6.fr \
--cc=corbet@lwn.net \
--cc=diaconita.tamara@gmail.com \
--cc=diaconitatamara@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.