From: Timur Tabi <timur@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: <linuxppc-dev@ozlabs.org>, <wim@iguana.be>,
<linux-watchdog@vger.kernel.org>
Subject: Re: [PATCH] watchdog: booke_wdt: clean up status messages
Date: Tue, 8 Feb 2011 10:33:22 -0600 [thread overview]
Message-ID: <4D517052.7050003@freescale.com> (raw)
In-Reply-To: <1297040772.14982.25.camel@pasglop>
Benjamin Herrenschmidt wrote:
> If you're going to cleanup the messages, then I think displaying:
>
> PowerPC Book-E Watchdog Timer Loaded
> booke_wdt: watchdog enabled (timeout = xxx sec)
>
> Isn't very nice.
>
> Lacks consistency ... you can prefix both lines the same way, or
> maybe better print only one line with all the necessary info.
Yeah, I see your point. I'll post a v2.
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, wim@iguana.be, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH] watchdog: booke_wdt: clean up status messages
Date: Tue, 8 Feb 2011 10:33:22 -0600 [thread overview]
Message-ID: <4D517052.7050003@freescale.com> (raw)
In-Reply-To: <1297040772.14982.25.camel@pasglop>
Benjamin Herrenschmidt wrote:
> If you're going to cleanup the messages, then I think displaying:
>
> PowerPC Book-E Watchdog Timer Loaded
> booke_wdt: watchdog enabled (timeout = xxx sec)
>
> Isn't very nice.
>
> Lacks consistency ... you can prefix both lines the same way, or
> maybe better print only one line with all the necessary info.
Yeah, I see your point. I'll post a v2.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-02-08 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 21:29 [PATCH] watchdog: booke_wdt: clean up status messages Timur Tabi
2011-02-07 1:06 ` Benjamin Herrenschmidt
2011-02-08 16:33 ` Timur Tabi [this message]
2011-02-08 16:33 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2011-01-17 21:28 Timur Tabi
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=4D517052.7050003@freescale.com \
--to=timur@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=wim@iguana.be \
/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.