From: Mitchel Humpherys <mitchelh@codeaurora.org>
To: Jungseok Lee <jays.lee@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, Catalin.Marinas@arm.com,
Marc Zyngier <Marc.Zyngier@arm.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
kgene.kim@samsung.com, steve.capper@linaro.org,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, ilho215.lee@samsung.com,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
sungjinn.chung@samsung.com
Subject: Re: [PATCH v4 1/7] arm64: Use pr_* instead of printk
Date: Tue, 29 Apr 2014 13:35:23 -0700 [thread overview]
Message-ID: <vnkwsioveuwk.fsf@mitchelh-linux.qualcomm.com> (raw)
In-Reply-To: <000101cf6367$c4c219f0$4e464dd0$@samsung.com> (Jungseok Lee's message of "Tue, 29 Apr 2014 13:59:14 +0900")
On Mon, Apr 28 2014 at 09:59:14 PM, Jungseok Lee <jays.lee@samsung.com> wrote:
> This patch fixed the following checkpatch complaint as using pr_*
> instead of printk.
>
> WARNING: printk() should include KERN_ facility level
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Signed-off-by: Jungseok Lee <jays.lee@samsung.com>
> Reviewed-by: Sungjinn Chung <sungjinn.chung@samsung.com>
> ---
> arch/arm64/kernel/traps.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index 7ffaddd..0484e81 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -65,7 +65,7 @@ static void dump_mem(const char *lvl, const char *str, unsigned long bottom,
> fs = get_fs();
> set_fs(KERNEL_DS);
>
> - printk("%s%s(0x%016lx to 0x%016lx)\n", lvl, str, bottom, top);
> + pr_emerg("%s%s(0x%016lx to 0x%016lx)\n", lvl, str, bottom, top);
Currently this printk is being called with lvl=KERN_EMERG or lvl="". In
the case of lvl=KERN_EMERG leaving lvl in is redundant. In the case of
lvl="" this is a behavioral change (printing to a different log
level). Was this intended?
>
> for (first = bottom & ~31; first < top; first += 32) {
> unsigned long p;
> @@ -83,7 +83,7 @@ static void dump_mem(const char *lvl, const char *str, unsigned long bottom,
> sprintf(str + i * 9, " ????????");
> }
> }
> - printk("%s%04lx:%s\n", lvl, first & 0xffff, str);
> + pr_emerg("%s%04lx:%s\n", lvl, first & 0xffff, str);
Ditto
> }
>
> set_fs(fs);
> @@ -124,7 +124,7 @@ static void dump_instr(const char *lvl, struct pt_regs *regs)
> break;
> }
> }
> - printk("%sCode: %s\n", lvl, str);
> + pr_emerg("%sCode: %s\n", lvl, str);
Ditto. Also called with with lvl=KERN_INFO.
Mitch
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-04-29 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 4:59 [PATCH v4 1/7] arm64: Use pr_* instead of printk Jungseok Lee
2014-04-29 20:35 ` Mitchel Humpherys [this message]
2014-04-30 2:32 ` Jungseok Lee
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=vnkwsioveuwk.fsf@mitchelh-linux.qualcomm.com \
--to=mitchelh@codeaurora.org \
--cc=Catalin.Marinas@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=arnd@arndb.de \
--cc=christoffer.dall@linaro.org \
--cc=ilho215.lee@samsung.com \
--cc=jays.lee@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=steve.capper@linaro.org \
--cc=sungjinn.chung@samsung.com \
/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