From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Change misleading warning when CONFIG_CMDLINE_FORCE is used
Date: Tue, 11 Jan 2011 23:18:39 +0000 [thread overview]
Message-ID: <20110111231839.GD3181@pulham.picochip.com> (raw)
In-Reply-To: <1294766953-6889-1-git-send-email-holler@ahsoftware.de>
Hi Alexander,
On Tue, Jan 11, 2011 at 06:29:13PM +0100, Alexander Holler wrote:
> When CONFIG_CMDLINE_FORCE is used, the warning
>
> Ignoring unrecognised tag 0x54410009
>
> was displayed. Change this to
>
> Ignoring tag cmdline (using the default kernel command line)
>
> Signed-off-by: Alexander Holler <holler@ahsoftware.de>
> ---
> arch/arm/kernel/setup.c | 8 ++++++--
> 1 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/kernel/setup.c b/arch/arm/kernel/setup.c
> index 336f14e..19c0e96 100644
> --- a/arch/arm/kernel/setup.c
> +++ b/arch/arm/kernel/setup.c
> @@ -649,15 +649,19 @@ static int __init parse_tag_revision(const struct tag *tag)
>
> __tagtable(ATAG_REVISION, parse_tag_revision);
>
> -#ifndef CONFIG_CMDLINE_FORCE
> static int __init parse_tag_cmdline(const struct tag *tag)
> {
> +#ifndef CONFIG_CMDLINE_FORCE
> strlcpy(default_command_line, tag->u.cmdline.cmdline, COMMAND_LINE_SIZE);
> +#else
> + printk(KERN_WARNING
> + "Ignoring tag cmdline"
> + " (using the default kernel command line)\n");
> +#endif /* CONFIG_CMDLINE_FORCE */
For strings in a printk() like this you don't need to split them to keep
them under 80 characters. This makes it harder to grep for so it's fine
(and preferred) to keep this on a single line.
Jamie
next prev parent reply other threads:[~2011-01-11 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 17:29 [PATCH] ARM: Change misleading warning when CONFIG_CMDLINE_FORCE is used Alexander Holler
2011-01-11 23:18 ` Jamie Iles [this message]
2011-01-11 23:28 ` Russell King - ARM Linux
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=20110111231839.GD3181@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.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