From: 명혁 <hyuk.myeong@lge.com>
To: <gregkh@linuxfoundation.org>, <jslaby@suse.cz>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH] Fix typo in the comment
Date: Wed, 3 Jun 2015 10:51:54 +0900 [thread overview]
Message-ID: <020e01d09d9f$de4fd880$9aef8980$@lge.com> (raw)
This patch fix a spelling typo in the comment in synclink.c and
synclinkmp.c.
Signed-off-by: Hyuk Myeong <hyuk.myeong@lge.com>
---
drivers/tty/synclink.c | 4 ++--
drivers/tty/synclinkmp.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/tty/synclink.c b/drivers/tty/synclink.c
index b799170..3bbb07c 100644
--- a/drivers/tty/synclink.c
+++ b/drivers/tty/synclink.c
@@ -7468,9 +7468,9 @@ static bool mgsl_memory_test( struct mgsl_struct
*info )
* memory.
*
* This function in effect, breaks the a large shared memory write
- * into multiple transations by interleaving a shared memory read
+ * into multiple transactions by interleaving a shared memory read
* which will flush the write FIFO and 'complete' the write
- * transation. This allows any pending DMA request to gain control
+ * transaction. This allows any pending DMA request to gain control
* of the local bus in a timely fasion.
*
* Arguments:
diff --git a/drivers/tty/synclinkmp.c b/drivers/tty/synclinkmp.c
index c3f9091..2ffcfe4 100644
--- a/drivers/tty/synclinkmp.c
+++ b/drivers/tty/synclinkmp.c
@@ -5415,9 +5415,9 @@ static bool memory_test(SLMP_INFO *info)
* and does not release the bus. This causes DMA latency problems
* at high speeds when copying large data blocks to the shared memory.
*
- * This function breaks a write into multiple transations by
+ * This function breaks a write into multiple transactions by
* interleaving a read which flushes the write FIFO and 'completes'
- * the write transation. This allows any pending DMA request to gain
control
+ * the write transaction. This allows any pending DMA request to gain
control
* of the local bus in a timely fasion.
*/
static void load_pci_memory(SLMP_INFO *info, char* dest, const char* src,
unsigned short count)
--
1.9.3
next reply other threads:[~2015-06-03 1:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 1:51 명혁 [this message]
2015-06-08 20:59 ` [PATCH] Fix typo in the comment Greg KH
-- strict thread matches above, loose matches on Subject: below --
2020-05-22 10:30 Hari
2020-05-28 22:53 ` Brown, Aaron F
2015-06-02 10:05 명혁
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='020e01d09d9f$de4fd880$9aef8980$@lge.com' \
--to=hyuk.myeong@lge.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).