From: Tamara Diaconita <diaconitatamara@gmail.com>
To: corbet@lwn.net, outreachy-kernel@googlegroups.com,
linux-doc@vger.kernel.org
Cc: Tamara Diaconita <diaconita.tamara@gmail.com>
Subject: [PATCH] Documentation: Fix typos
Date: Wed, 15 Mar 2017 19:58:11 +0200 [thread overview]
Message-ID: <20170315175811.4187-1-diaconita.tamara@gmail.com> (raw)
Fix typos in sync_file.txt to make documentation grammatically correct.
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
next reply other threads:[~2017-03-15 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 17:58 Tamara Diaconita [this message]
2017-03-15 20:07 ` [Outreachy kernel] [PATCH] Documentation: Fix typos Julia Lawall
2017-03-15 21:56 ` Alison Schofield
2017-03-15 21:57 ` Julia Lawall
2017-03-15 22:10 ` Jonathan Corbet
-- strict thread matches above, loose matches on Subject: below --
2017-03-15 17:54 Tamara Diaconita
2017-03-15 17:57 ` 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=20170315175811.4187-1-diaconita.tamara@gmail.com \
--to=diaconitatamara@gmail.com \
--cc=corbet@lwn.net \
--cc=diaconita.tamara@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.