linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@iguana.be>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: wim@iguana.be, linux-watchdog@vger.kernel.org,
	Timur Tabi <timur@freescale.com>,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [v2] watchdog: booke_wdt: clean up status messages
Date: Tue, 15 Mar 2011 19:19:04 +0100	[thread overview]
Message-ID: <20110315181904.GM1751@infomag.iguana.be> (raw)
In-Reply-To: <C8B1E427-5A9D-4ED2-9C39-C1D8201E636E@kernel.crashing.org>

Hi Kumar,

I allready had it in the watchdog tree for a couple of weeks (and thus also in linux-next).
Are you going to sent it of to Linus or will I sent it over via the watchdog tree?

Thanks in advance,
Wim.

> 
> On Feb 8, 2011, at 5:39 PM, Timur Tabi wrote:
> 
> > Improve the status messages that are displayed during some operations of the
> > PowerPC watchdog timer driver.  When the watchdog is enabled, the timeout is
> > displayed as a number of seconds, instead of an obscure "period".  The "period"
> > is the position of a bit in a 64-bit timer register.  The higher the value,
> > the quicker the watchdog timeout occurs.  Some people chose a high "period"
> > value for the timer and get confused as to why the board resets within a
> > few seconds.
> > 
> > Messages displayed during open and close are now debug messages, so that they
> > don't clutter the console by default.  Finally, printk() is replaced with the
> > pr_xxx() equivalent.
> > 
> > Signed-off-by: Timur Tabi <timur@freescale.com>
> > ---
> > drivers/watchdog/booke_wdt.c |   19 +++++++++----------
> > 1 files changed, 9 insertions(+), 10 deletions(-)
> 
> applied
> 
> - k

  reply	other threads:[~2011-03-15 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 23:39 [PATCH] [v2] watchdog: booke_wdt: clean up status messages Timur Tabi
2011-03-15 15:42 ` Kumar Gala
2011-03-15 18:19   ` Wim Van Sebroeck [this message]
2011-03-15 18:47     ` Kumar Gala

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=20110315181904.GM1751@infomag.iguana.be \
    --to=wim@iguana.be \
    --cc=galak@kernel.crashing.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.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;
as well as URLs for NNTP newsgroup(s).