From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: James.Bottomley@HansenPartnership.com, deller@gmx.de,
unixbhaskar@gmail.com, linux-parisc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: rdunlap@infradead.org
Subject: [PATCH V3] parisc: math-emu: Few spelling fixes in the file fpu.h
Date: Thu, 18 Mar 2021 00:54:27 +0530 [thread overview]
Message-ID: <20210317192427.2050913-1-unixbhaskar@gmail.com> (raw)
s/synopis/synopsis/
s/differeniate/differentiate/
s/differeniation/differentiation/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
Changes from V2:
Incorporated the changes suggested by Randy
arch/parisc/math-emu/fpu.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/parisc/math-emu/fpu.h b/arch/parisc/math-emu/fpu.h
index 853c19c03828..ea1c8c3539c6 100644
--- a/arch/parisc/math-emu/fpu.h
+++ b/arch/parisc/math-emu/fpu.h
@@ -12,7 +12,7 @@
* @(#) pa/fp/fpu.h $Revision: 1.1 $
*
* Purpose:
- * <<please update with a synopis of the functionality provided by this file>>
+ * <<please update with a synopsis of the functionality provided by this file>>
*
*
* END_DESC
@@ -50,9 +50,9 @@
#define EMULATION_VERSION 4
/*
- * The only was to differeniate between TIMEX and ROLEX (or PCX-S and PCX-T)
- * is thorough the potential type field from the PDC_MODEL call. The
- * following flags are used at assist this differeniation.
+ * The only way to differentiate between TIMEX and ROLEX (or PCX-S and PCX-T)
+ * is through the potential type field from the PDC_MODEL call. The
+ * following flags are used to assist this differentiation.
*/
#define ROLEX_POTENTIAL_KEY_FLAGS PDC_MODEL_CPU_KEY_WORD_TO_IO
--
2.30.2
next reply other threads:[~2021-03-17 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 19:24 Bhaskar Chowdhury [this message]
2021-03-17 20:15 ` [PATCH V3] parisc: math-emu: Few spelling fixes in the file fpu.h Randy Dunlap
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=20210317192427.2050913-1-unixbhaskar@gmail.com \
--to=unixbhaskar@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=rdunlap@infradead.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).