From: Rob Herring <robh@kernel•org>
To: Eugen.Hristev@microchip•com
Cc: devicetree@vger•kernel.org, alexandre.belloni@bootlin•com,
linux-watchdog@vger•kernel.org, linux-kernel@vger•kernel.org,
robh+dt@kernel•org, linux-arm-kernel@lists•infradead.org,
Eugen.Hristev@microchip•com, wim@linux-watchdog•org,
linux@roeck-us•net
Subject: Re: [PATCH v2 1/2] dt-bindings: watchdog: sama5d4_wdt: add microchip,sam9x60-wdt compatible
Date: Fri, 25 Oct 2019 16:33:34 -0500 [thread overview]
Message-ID: <20191025213334.GA23280@bogus> (raw)
In-Reply-To: <1571648890-15140-1-git-send-email-eugen.hristev@microchip.com>
On Mon, 21 Oct 2019 09:14:05 +0000, <Eugen.Hristev@microchip•com> wrote:
>
> From: Eugen Hristev <eugen.hristev@microchip•com>
>
> The Atmel sama5d4_wdt needs to be compatible with microchip,sam9x60-wdt
> The sama5d4_wdt driver is updated to work with both hardware blocks
> (sama5d4/sama5d2 and sam9x60 based blocks)
>
> Signed-off-by: Eugen Hristev <eugen.hristev@microchip•com>
> ---
> Documentation/devicetree/bindings/watchdog/atmel-sama5d4-wdt.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel•org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-25 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 9:14 [PATCH v2 1/2] dt-bindings: watchdog: sama5d4_wdt: add microchip,sam9x60-wdt compatible Eugen.Hristev
2019-10-21 9:14 ` [PATCH v2 2/2] watchdog: sama5d4_wdt: addition of sam9x60 compatible watchdog Eugen.Hristev
2019-10-29 13:28 ` Guenter Roeck
2019-11-07 12:51 ` Eugen.Hristev
2019-11-07 16:41 ` Guenter Roeck
2019-11-07 17:10 ` Eugen.Hristev
2019-10-25 21:33 ` Rob Herring [this message]
2019-10-29 13:16 ` [PATCH v2 1/2] dt-bindings: watchdog: sama5d4_wdt: add microchip,sam9x60-wdt compatible Guenter Roeck
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=20191025213334.GA23280@bogus \
--to=robh@kernel$(echo .)org \
--cc=Eugen.Hristev@microchip$(echo .)com \
--cc=alexandre.belloni@bootlin$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-watchdog@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=robh+dt@kernel$(echo .)org \
--cc=wim@linux-watchdog$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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