From: "Justin P. Mattock" <justinmattock@gmail.com>
To: trivial@kernel.org
Cc: linux-kernel@vger.kernel.org,
"Justin P. Mattock" <justinmattock@gmail.com>
Subject: [PATCH] Clean-up a few comments.
Date: Tue, 26 Jan 2010 15:39:38 -0800 [thread overview]
Message-ID: <1264549178-2874-1-git-send-email-justinmattock@gmail.com> (raw)
Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
---
arch/x86/kernel/setup.c | 9 ++++-----
1 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index f7b8b98..1bd37e9 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -245,7 +245,7 @@ struct edd edd;
#ifdef CONFIG_EDD_MODULE
EXPORT_SYMBOL(edd);
#endif
-/**
+/*
* copy_edd() - Copy the BIOS EDD information
* from boot_params into a safe place.
*
@@ -398,8 +398,8 @@ static void __init reserve_initrd(void)
if (ramdisk_end <= end_of_lowmem) {
/* All in lowmem, easy case */
- /*
- * don't need to reserve again, already reserved early
+
+ /* don't need to reserve again, already reserved early
* in i386_start_kernel
*/
initrd_start = ramdisk_image + PAGE_OFFSET;
@@ -665,8 +665,7 @@ static struct dmi_system_id __initdata bad_bios_dmi_table[] = {
* for initialization. Note, the efi init code path is determined by the
* global efi_enabled. This allows the same kernel image to be used on existing
* systems (with a traditional BIOS) as well as on EFI systems.
- */
-/*
+ *
* setup_arch - architecture-specific boot-time initializations
*
* Note: On x86_64, fixmaps are ready for use even before this is called.
--
1.6.5.GIT
next reply other threads:[~2010-01-26 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 23:39 Justin P. Mattock [this message]
2010-01-26 23:45 ` [PATCH] Clean-up a few comments Jiri Kosina
2010-01-27 0:01 ` Justin P. Mattock
2010-01-27 3:11 ` Américo Wang
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=1264549178-2874-1-git-send-email-justinmattock@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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