mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: rneha725 <rneha725@gmail.com>
To: rneha725@gmail.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] Staging: atm: fix 'endianess' spelling to 'endianness' in fore200e.c This is a patch to the fore200e that fixes the spelling of 'endianess' to the correct one, that is, 'endianness' found by checkpatch.pl tool
Date: Thu, 10 Mar 2016 11:00:38 +0530	[thread overview]
Message-ID: <1457587838-7091-1-git-send-email-rneha725@gmail.com> (raw)

Signed-off-by: Neha Rani <rneha725@gmail.com>
---
 drivers/atm/fore200e.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/atm/fore200e.c b/drivers/atm/fore200e.c
index 75dde90..fac5e4fd 100644
--- a/drivers/atm/fore200e.c
+++ b/drivers/atm/fore200e.c
@@ -409,7 +409,7 @@ fore200e_shutdown(struct fore200e* fore200e)
 static u32 fore200e_pca_read(volatile u32 __iomem *addr)
 {
     /* on big-endian hosts, the board is configured to convert
-       the endianess of slave RAM accesses  */
+       the endianness of slave RAM accesses  */
     return le32_to_cpu(readl(addr));
 }
 
@@ -417,7 +417,7 @@ static u32 fore200e_pca_read(volatile u32 __iomem *addr)
 static void fore200e_pca_write(u32 val, volatile u32 __iomem *addr)
 {
     /* on big-endian hosts, the board is configured to convert
-       the endianess of slave RAM accesses  */
+       the endianness of slave RAM accesses  */
     writel(cpu_to_le32(val), addr);
 }
 
@@ -577,7 +577,7 @@ static int fore200e_pca_configure(struct fore200e *fore200e)
 
     master_ctrl = master_ctrl
 #if defined(__BIG_ENDIAN)
-	/* request the PCA board to convert the endianess of slave RAM accesses */
+	/* request the PCA board to convert the endianness of slave RAM accesses */
 	| PCA200E_CTRL_CONVERT_ENDIAN
 #endif
 #if 0
-- 
2.5.0

             reply	other threads:[~2016-03-10  5:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10  5:30 rneha725 [this message]
2016-03-10  6:17 ` Amitoj Kaur Chawla

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=1457587838-7091-1-git-send-email-rneha725@gmail.com \
    --to=rneha725@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --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

all inboxes | Powered by JetHome®