public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jisheng Zhang <jszhang@marvell.com>,
	robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
	catalin.marinas@arm.com, will.deacon@arm.com
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] arm: dts: berlin: enable all dw_wdt nodes unconditionally
Date: Wed, 6 Jul 2016 19:58:56 +0200	[thread overview]
Message-ID: <577D46E0.7040404@gmail.com> (raw)
In-Reply-To: <1467787301-3728-1-git-send-email-jszhang@marvell.com>

On 06.07.2016 08:41, Jisheng Zhang wrote:
> When we add watchdog dt nodes into berlin dtsi, the dw_wdt driver can't
> support multiple variants, so we have to keep one enabled and others
> disabled. After commit f29a72c24ad4 ("watchdog: dw_wdt: Convert to use
> watchdog infrastructure"), the dw_wdt driver can support multiple
> variants, so we can unconditionally enable all dw_wdt nodes now.
> 
> Jisheng Zhang (3):
>   arm: dts: berlin2: enable all wdt nodes unconditionally
>   arm: dts: berlin2q: enable all wdt nodes unconditionally
>   arm64: dts: berlin4ct: enable all wdt nodes unconditionally

Applied all three to berlin/dt and berlin64/dt respectively.

Thanks!

Sebastian

>  arch/arm/boot/dts/berlin2.dtsi             | 2 --
>  arch/arm/boot/dts/berlin2q.dtsi            | 2 --
>  arch/arm64/boot/dts/marvell/berlin4ct.dtsi | 2 --
>  3 files changed, 6 deletions(-)
> 

      parent reply	other threads:[~2016-07-06 17:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  6:41 [PATCH 0/3] arm: dts: berlin: enable all dw_wdt nodes unconditionally Jisheng Zhang
2016-07-06  6:41 ` [PATCH 1/3] arm: dts: berlin2: enable all wdt " Jisheng Zhang
2016-07-06  6:41 ` [PATCH 2/3] arm: dts: berlin2q: " Jisheng Zhang
2016-07-06  6:41 ` [PATCH 3/3] arm64: dts: berlin4ct: " Jisheng Zhang
2016-07-06 17:58 ` Sebastian Hesselbarth [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=577D46E0.7040404@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jszhang@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=will.deacon@arm.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