All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aron Griffis <aron@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2 of 4] Spelling/punctuation fixes
Date: Wed, 12 Dec 2007 15:43:23 +0000	[thread overview]
Message-ID: <20071212154323.GI4241@fc.hp.com> (raw)
In-Reply-To: <049467433cda01769d2f.1197472069@jenkins.nashua>

I guess I forgot my signoff on this one, if it matters for spelling
fixes...

# HG changeset patch
# User Aron Griffis <aron@hp.com>
# Date 1197470463 18000
# Node ID 049467433cda01769d2f8c276fcfeb7d216658d7
# Parent  1161690ae81590dec4e97c52f07cf1798c11a97b
Spelling/punctuation fixes

Woah is not a word ;-)

Signed-off-by: Aron Griffis <aron@hp.com>

diff -r 1161690ae815 -r 049467433cda arch/ia64/kernel/efi.c
--- a/arch/ia64/kernel/efi.c	Tue Dec 11 21:53:55 2007 -0500
+++ b/arch/ia64/kernel/efi.c	Wed Dec 12 09:41:03 2007 -0500
@@ -331,7 +331,7 @@ efi_memmap_walk_uc (efi_freemem_callback
 }
 
 /*
- * Look for the PAL_CODE region reported by EFI and maps it using an
+ * Looks for the PAL_CODE region reported by EFI and maps it using an
  * ITR to enable safe PAL calls in virtual mode.  See IA-64 Processor
  * Abstraction Layer chapter 11 in ADAG
  */
@@ -372,7 +372,7 @@ efi_get_pal_addr (void)
 		 * PAL code is guaranteed to be aligned on a power of 2 between
 		 * 4k and 256KB and that only one ITR is needed to map it. This
 		 * implies that the PAL code is always aligned on its size,
-		 * i.e., the closest matching page size supported by the TLB.
+		 * i.e. the closest matching page size supported by the TLB.
 		 * Therefore PAL code is guaranteed never to cross a 64MB unless
 		 * it is bigger than 64MB (very unlikely!).  So for now the
 		 * following test is enough to determine whether or not we need
@@ -385,7 +385,7 @@ efi_get_pal_addr (void)
 		}
 
 		if (md->num_pages << EFI_PAGE_SHIFT > IA64_GRANULE_SIZE)
-			panic("Woah!  PAL code size bigger than a granule!");
+			panic("Whoa!  PAL code size bigger than a granule!");
 
 #if EFI_DEBUG
 		mask  = ~((1 << IA64_GRANULE_SHIFT) - 1);
@@ -435,7 +435,7 @@ efi_init (void)
 	int i;
 
 	/*
-	 * it's too early to be able to use the standard kernel command line
+	 * It's too early to be able to use the standard kernel command line
 	 * support...
 	 */
 	for (cp = boot_command_line; *cp; ) {
@@ -465,9 +465,9 @@ efi_init (void)
 	 * Verify the EFI Table
 	 */
 	if (efi.systab = NULL)
-		panic("Woah! Can't find EFI system table.\n");
+		panic("Whoa! Can't find EFI system table.\n");
 	if (efi.systab->hdr.signature != EFI_SYSTEM_TABLE_SIGNATURE)
-		panic("Woah! EFI system table signature incorrect\n");
+		panic("Whoa! EFI system table signature incorrect\n");
 	if ((efi.systab->hdr.revision >> 16) = 0)
 		printk(KERN_WARNING "Warning: EFI system table version "
 		       "%d.%02d, expected 1.00 or greater\n",
@@ -1201,7 +1201,7 @@ efi_initialize_iomem_resources(struct re
 		if ((res = kzalloc(sizeof(struct resource),
 				   GFP_KERNEL)) = NULL) {
 			printk(KERN_ERR 
-			       "failed to alocate resource for iomem\n");
+			       "failed to allocate resource for iomem\n");
 			return;
 		}
 

  reply	other threads:[~2007-12-12 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 15:07 [PATCH 2 of 4] Spelling/punctuation fixes Aron Griffis
2007-12-12 15:43 ` Aron Griffis [this message]
2007-12-13 23:30 ` Peter Chubb
2007-12-13 23:52 ` Aron Griffis

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=20071212154323.GI4241@fc.hp.com \
    --to=aron@hp.com \
    --cc=linux-ia64@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 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.