Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: wim@iguana.be
Cc: linux-watchdog@vger.kernel.org, zajec5@gmail.com,
	linux-mips@linux-mips.org
Subject: Re: [PATCH v4 0/5] watchdog: bcm47xx_wdt.c: add support for SoCs with PMU
Date: Thu, 24 Jan 2013 18:15:57 +0100	[thread overview]
Message-ID: <51016C4D.40707@hauke-m.de> (raw)
In-Reply-To: <1358010851-28077-1-git-send-email-hauke@hauke-m.de>

On 01/12/2013 06:14 PM, Hauke Mehrtens wrote:
> This patch series improves the functions for setting the watchdog 
> driver for bcm47xx based SoCs using ssb and bcma. This makes the 
> watchdog driver use the platform device provided by bcma or ssb.
> 
> This code is currently based on the linux-watchdog/master tree by 
> Wim Van Sebroeck.
> 
> v4:
>  * Just the parts changing the watchdog driver itself and not ssb or bcma.
> 
> v3:
>  * Remove changes done to the watchdog driver so John could pull this 
>    into wireless-testing, this sill works with the old watchdog driver. 
>    The patches changing the watchdog driver will be send later.
>    This was done to get this into 3.8 because Wim Van Sebroeck is 
>    neither giving an Ack or a Nack on these patches and we want to do 
>    more changes to bcma/ssb on top of these.
> 
> v2:
>  * reword some commit messages
>  * rebase on current wireless-testing/master with 
>       "ssb: extif: fix compile errors" applied on top of it.
>  * do not change value of WDT_SOFTTIMER_MAX
>  * moved some small changes in the bcm47xx_wdt.c patches
> 
> Hauke Mehrtens (5):
>   watchdog: bcm47xx_wdt.c: convert to watchdog core api
>   watchdog: bcm47xx_wdt.c: use platform device
>   watchdog: bcm47xx_wdt.c: rename ops methods
>   watchdog: bcm47xx_wdt.c: rename wdt_time to timeout
>   watchdog: bcm47xx_wdt.c: add hard timer
> 
>  drivers/watchdog/Kconfig       |    1 +
>  drivers/watchdog/bcm47xx_wdt.c |  339 +++++++++++++++++-----------------------
>  include/linux/bcm47xx_wdt.h    |    9 ++
>  3 files changed, 154 insertions(+), 195 deletions(-)
> 
Hi Wim,

what is the status of these patches?

Hauke

  parent reply	other threads:[~2013-01-24 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12 17:14 [PATCH v4 0/5] watchdog: bcm47xx_wdt.c: add support for SoCs with PMU Hauke Mehrtens
2013-01-12 17:14 ` [PATCH v4 1/5] watchdog: bcm47xx_wdt.c: convert to watchdog core api Hauke Mehrtens
2013-01-12 17:14 ` [PATCH v4 2/5] watchdog: bcm47xx_wdt.c: use platform device Hauke Mehrtens
2013-01-24 17:13   ` [PATCH v5 " Hauke Mehrtens
2013-01-12 17:14 ` [PATCH v4 3/5] watchdog: bcm47xx_wdt.c: rename ops methods Hauke Mehrtens
2013-01-12 17:14 ` [PATCH v4 4/5] watchdog: bcm47xx_wdt.c: rename wdt_time to timeout Hauke Mehrtens
2013-01-12 17:14 ` [PATCH v4 5/5] watchdog: bcm47xx_wdt.c: add hard timer Hauke Mehrtens
2013-01-24 17:15 ` Hauke Mehrtens [this message]
2013-01-28 21:35   ` [PATCH v4 0/5] watchdog: bcm47xx_wdt.c: add support for SoCs with PMU Wim Van Sebroeck
2013-01-28 22:06     ` Hauke Mehrtens
2013-02-07 22:29 ` Wim Van Sebroeck

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=51016C4D.40707@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=wim@iguana.be \
    --cc=zajec5@gmail.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