From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org,
Michael Demeter <michael.demeter@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH] Added some addition debug prints for pb_keys
Date: Sun, 18 Dec 2011 09:36:14 +0100 [thread overview]
Message-ID: <20111218083614.GF4144@elte.hu> (raw)
In-Reply-To: <20111215223116.10166.50803.stgit@bob.linux.org.uk>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> From: Michael Demeter <michael.demeter@intel.com>
>
> Added additional debug output that we always seem to add
> during power ons to validate firmware operation.
>
> Signed-off-by: Michael Demeter <michael.demeter@intel.com>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> ---
>
> arch/x86/platform/mrst/mrst.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
>
> diff --git a/arch/x86/platform/mrst/mrst.c b/arch/x86/platform/mrst/mrst.c
> index a9a4732..3002cc86 100644
> --- a/arch/x86/platform/mrst/mrst.c
> +++ b/arch/x86/platform/mrst/mrst.c
> @@ -1035,6 +1035,8 @@ static int __init pb_keys_init(void)
> num = sizeof(gpio_button) / sizeof(struct gpio_keys_button);
> for (i = 0; i < num; i++) {
> gb[i].gpio = get_gpio_by_name(gb[i].desc);
> + pr_debug("info[%2d]: name = %s,"
> + "gpio = %d\n", i, gb[i].desc, gb[i].gpio);
I've fixed this to lie on a single line - there's no point in
line-breaking pr_debug()s in general - especially not the format
string.
Note that merging the format string unearthed a small formatting
ugly:
"info[%2d]: name = %s,gpio = %d\n"
I edited that to the probably intended:
"info[%2d]: name = %s, gpio = %d\n"
Thanks,
Ingo
next prev parent reply other threads:[~2011-12-18 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 22:31 Alan Cox
2011-12-18 8:36 ` Ingo Molnar [this message]
2011-12-18 23:53 ` [tip:x86/platform] x86/mrst: Add additional " tip-bot for Michael Demeter
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=20111218083614.GF4144@elte.hu \
--to=mingo@elte.hu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.demeter@intel.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
Powered by JetHome