All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Alexey Klimov <alexey.klimov@linaro.org>,
	daniel.lezcano@linaro.org, linux-mediatek@lists.infradead.org
Cc: yingjoe.chen@mediatek.com, tglx@linutronix.de,
	linux-kernel@vger.kernel.org, klimov.linux@gmail.com
Subject: Re: [RFC PATCH 1/3] clocksource: mtk_timer: add pr_fmt define
Date: Fri, 4 Sep 2015 10:51:33 +0200	[thread overview]
Message-ID: <55E95B95.4030207@gmail.com> (raw)
In-Reply-To: <1441336900-15095-1-git-send-email-alexey.klimov@linaro.org>



On 04/09/15 05:21, Alexey Klimov wrote:
> It's a bit uncler what subsystem/driver emits some messages
> to dmesg in function mtk_init_timer().
> Use pr_fmt to auto-prefix the messages appropriately.
>
> Signed-off-by: Alexey Klimov <alexey.klimov@linaro.org>

Acked-by: Matthias Brugger <matthias.bgg@gmail.com>

> ---
>   drivers/clocksource/mtk_timer.c | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clocksource/mtk_timer.c b/drivers/clocksource/mtk_timer.c
> index 50f0641..ca5ea9e 100644
> --- a/drivers/clocksource/mtk_timer.c
> +++ b/drivers/clocksource/mtk_timer.c
> @@ -16,6 +16,8 @@
>    * GNU General Public License for more details.
>    */
>
> +#define pr_fmt(fmt)	KBUILD_MODNAME ": " fmt
> +
>   #include <linux/clk.h>
>   #include <linux/clockchips.h>
>   #include <linux/interrupt.h>
>

      parent reply	other threads:[~2015-09-04  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  3:21 [RFC PATCH 1/3] clocksource: mtk_timer: add pr_fmt define Alexey Klimov
2015-09-04  3:21 ` [RFC PATCH 2/3] clocksource: mtk_timer: change pr_warn()s to pr_err()s in mtk_timer_init Alexey Klimov
2015-09-04  3:40   ` Joe Perches
2015-09-04  8:50   ` Matthias Brugger
2015-09-04  3:21 ` [RFC PATCH 3/3] clocksource: mtk_timer: fix memleak in mtk_timer_init() Alexey Klimov
     [not found]   ` <1441336900-15095-3-git-send-email-alexey.klimov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-09-04  8:39     ` Matthias Brugger
2015-09-04  8:39       ` Matthias Brugger
2015-09-04  8:51 ` Matthias Brugger [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=55E95B95.4030207@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=alexey.klimov@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=klimov.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=tglx@linutronix.de \
    --cc=yingjoe.chen@mediatek.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 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.