From: Len Brown <lenb@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Len Brown <len.brown@intel.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, stable@kernel.org
Subject: Re: linux-next: build warningiIn Linus' tree
Date: Sun, 29 May 2011 23:47:52 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.02.1105292346340.10035@arrandale.kernel.org> (raw)
In-Reply-To: <20110530114828.8ef6625b.sfr@canb.auug.org.au>
From: Len Brown <len.brown@intel.com>
Date: Sun, 29 May 2011 23:38:15 -0400
Subject: [PATCH] x86 idle: fix build warning for WARN_ONCE("idle=mwait")
In 5d4c47e0195b989f284907358bd5c268a44b91c7
"x86 idle: deprecate mwait_idle() and "idle=mwait" cmdline param"...
I fat-fingered the editing when I updated the WARN_ONCE() string:
arch/x86/kernel/process.c: In function 'idle_setup':
arch/x86/kernel/process.c:645:1: warning: unknown escape sequence: '\i'
remove the '\n' while we are here, it works fine without it.
Signed-off-by: Len Brown <len.brown@intel.com>
---
arch/x86/kernel/process.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
index 426a5b6..c54f87d 100644
--- a/arch/x86/kernel/process.c
+++ b/arch/x86/kernel/process.c
@@ -642,7 +642,7 @@ static int __init idle_setup(char *str)
boot_option_idle_override = IDLE_POLL;
} else if (!strcmp(str, "mwait")) {
boot_option_idle_override = IDLE_FORCE_MWAIT;
- WARN_ONCE(1, "\idle=mwait\" will be removed in 2012\"\n");
+ WARN_ONCE(1, "\"idle=mwait\" will be removed in 2012");
} else if (!strcmp(str, "halt")) {
/*
* When the boot option of idle=halt is added, halt is
--
1.7.4.4
next prev parent reply other threads:[~2011-05-30 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 1:48 linux-next: build warningiIn Linus' tree Stephen Rothwell
2011-05-30 3:47 ` Len Brown [this message]
2011-05-30 7:34 ` Ingo Molnar
2011-05-30 19:11 ` Brown, Len
2011-05-30 19:23 ` Ingo Molnar
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=alpine.LFD.2.02.1105292346340.10035@arrandale.kernel.org \
--to=lenb@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stable@kernel.org \
--cc=x86@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