From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Moses Christopher <moseschristopherb@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clocksource: timer-probe: change log level to warn
Date: Tue, 16 Apr 2019 19:32:35 +0200 [thread overview]
Message-ID: <63ead988-cb06-ca14-6995-9d5405f3e562@linaro.org> (raw)
In-Reply-To: <20190416172309.7428-1-moseschristopherb@gmail.com>
On 16/04/2019 19:23, Moses Christopher wrote:
> - In drivers/clocksource/timer-probe.c, the log level for the message
> stating "no matching timers found" should be of warning(4) rather
> than critical(2)
> - Reference:
> - https://e2e.ti.com/support/processors/f/791/t/726024
> - As per the feedback received from Daniel Lezcano
>
> Signed-off-by: Moses Christopher <moseschristopherb@gmail.com>
Applied for 5.2 but massaged a bit the change log to comply with the
kernel submitting patches rules.
> ---
> drivers/clocksource/timer-probe.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/timer-probe.c b/drivers/clocksource/timer-probe.c
> index 028075720334..246b45d22d08 100644
> --- a/drivers/clocksource/timer-probe.c
> +++ b/drivers/clocksource/timer-probe.c
> @@ -50,5 +50,5 @@ void __init timer_probe(void)
> timers += acpi_probe_device_table(timer);
>
> if (!timers)
> - pr_crit("%s: no matching timers found\n", __func__);
> + pr_warn("%s: no matching timers found\n", __func__);
> }
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2019-04-16 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 17:23 Moses Christopher
2019-04-16 17:32 ` Daniel Lezcano [this message]
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=63ead988-cb06-ca14-6995-9d5405f3e562@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moseschristopherb@gmail.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®