All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@imgtec.com>
To: Guenter Roeck <linux@roeck-us.net>, Wim Van Sebroeck <wim@iguana.be>
Cc: <linux-watchdog@vger.kernel.org>,
	Andrew Bresticker <abrestic@chromium.org>,
	James Hogan <james.hogan@imgtec.com>,
	James Hartley <james.hartley@imgtec.com>,
	Naidu Tellapati <naidu.tellapati@imgtec.com>
Subject: Re: [PATCH 0/2] watchdog: imgpdc_wdt assorted fixes
Date: Thu, 21 May 2015 10:57:53 -0300	[thread overview]
Message-ID: <555DE461.2070002@imgtec.com> (raw)
In-Reply-To: <1431366065-16281-1-git-send-email-ezequiel.garcia@imgtec.com>

Wim,

Do you plan to take this for v4.2?

Thanks!

On 05/11/2015 02:41 PM, Ezequiel Garcia wrote:
> Hi,
> 
> A couple more fixes for IMG watchdog driver.
> 
> This first patch corrects the max_timeout setting which was wrongly
> set in cycles.
> 
> The second patch documents the driver's timeout round-up, which
> might seem a bit unintuitive. See the patch for more details.
> 
> Both patches are based on the three imgpdc patches sent recently by
> Andrew Bresticker [1].
> 
> [1] http://www.spinics.net/lists/linux-watchdog/msg06107.html
> 
> Thanks!
> 
> Ezequiel Garcia (2):
>   watchdog: imgpdc: Fix max timeout
>   watchdog: imgpdc: Add some documentation about the timeout
> 

-- 
Ezequiel

  parent reply	other threads:[~2015-05-21 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 17:41 [PATCH 0/2] watchdog: imgpdc_wdt assorted fixes Ezequiel Garcia
2015-05-11 17:41 ` [PATCH 1/2] watchdog: imgpdc: Fix max timeout Ezequiel Garcia
2015-05-12  3:13   ` Guenter Roeck
2015-05-12  4:14     ` Naidu Tellapati
2015-05-11 17:41 ` [PATCH 2/2] watchdog: imgpdc: Add some documentation about the timeout Ezequiel Garcia
2015-05-12  3:13   ` Guenter Roeck
2015-05-12  4:12     ` Naidu Tellapati
2015-05-21 13:57 ` Ezequiel Garcia [this message]
2015-06-01 22:57   ` [PATCH 0/2] watchdog: imgpdc_wdt assorted fixes Ezequiel Garcia

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=555DE461.2070002@imgtec.com \
    --to=ezequiel.garcia@imgtec.com \
    --cc=abrestic@chromium.org \
    --cc=james.hartley@imgtec.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=naidu.tellapati@imgtec.com \
    --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.