From: Fabio Estevam <festevam@gmail.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH v2] clk: Print the clock name and warning cause
Date: Wed, 14 Mar 2018 08:54:39 -0300 [thread overview]
Message-ID: <CAOMZO5DjQVkQeNfz7mYQwp8HtnWqKgWvj4NKZpB77x_WJwRyPA@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdXyEBaaGq8yS8Xdxj-0s-CirV3htBaVpN_oK_n9iWLArg@mail.gmail.com>
Hi Stephen,
On Wed, Jan 17, 2018 at 6:14 AM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Tue, Jan 16, 2018 at 1:50 PM, Fabio Estevam <fabio.estevam@nxp.com> wrote:
>> When getting the clock related warnings, it is useful to know what
>> is the clock name that is causing the problem and the cause of the
>> problem.
>>
>> Add the clock name and the the warning cause to the log, so that the
>> output becomes clearer like this:
>>
>> [ 2.383969] ------------[ cut here ]------------
>> [ 2.388720] WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:814 clk_core_disable+0xd4/0xf8
>> [ 2.396658] uart4_ipg_gate already disabled
>>
>> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Any comments, please?
next prev parent reply other threads:[~2018-03-14 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 12:50 [PATCH v2] clk: Print the clock name and warning cause Fabio Estevam
2018-01-17 8:14 ` Geert Uytterhoeven
2018-03-14 11:54 ` Fabio Estevam [this message]
2018-03-16 23:29 ` Stephen Boyd
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=CAOMZO5DjQVkQeNfz7mYQwp8HtnWqKgWvj4NKZpB77x_WJwRyPA@mail.gmail.com \
--to=festevam@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=geert@linux-m68k.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.