From: Daniel Palmer <daniel@0x0f.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Romain Perier <romain.perier@gmail.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Rob Herring <robh+dt@kernel.org>,
Mohammed Billoo <mohammed.billoo@gmail.com>,
linux-watchdog@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] Add watchdog for Mstar SoCs
Date: Sun, 13 Jun 2021 02:10:37 +0900 [thread overview]
Message-ID: <CAFr9PX=j3UxbawtuvQnyoToH=3iT_k+j_LByUF-uDd0yDOk2ZQ@mail.gmail.com> (raw)
In-Reply-To: <20210612125915.GA320112@roeck-us.net>
Hi Guenter, Romain,
On Sat, 12 Jun 2021 at 21:59, Guenter Roeck <linux@roeck-us.net> wrote:
> This works better. I applied patches 1 & 2 to my watchdog-next branch for
> hand-off to Wim. Note that the arm dts patch needs to be pushed through the
> arm tree.
I will take the dts patch and send a PR with it to the arm tree.
Cheers,
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Palmer <daniel@0x0f.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Romain Perier <romain.perier@gmail.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Rob Herring <robh+dt@kernel.org>,
Mohammed Billoo <mohammed.billoo@gmail.com>,
linux-watchdog@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] Add watchdog for Mstar SoCs
Date: Sun, 13 Jun 2021 02:10:37 +0900 [thread overview]
Message-ID: <CAFr9PX=j3UxbawtuvQnyoToH=3iT_k+j_LByUF-uDd0yDOk2ZQ@mail.gmail.com> (raw)
In-Reply-To: <20210612125915.GA320112@roeck-us.net>
Hi Guenter, Romain,
On Sat, 12 Jun 2021 at 21:59, Guenter Roeck <linux@roeck-us.net> wrote:
> This works better. I applied patches 1 & 2 to my watchdog-next branch for
> hand-off to Wim. Note that the arm dts patch needs to be pushed through the
> arm tree.
I will take the dts patch and send a PR with it to the arm tree.
Cheers,
Daniel
_______________________________________________
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:[~2021-06-12 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 20:07 [PATCH v4 0/3] Add watchdog for Mstar SoCs Romain Perier
2021-06-11 20:07 ` Romain Perier
2021-06-11 20:07 ` [PATCH v4 1/3] dt-bindings: watchdog: Add Mstar MSC313e WDT devicetree bindings documentation Romain Perier
2021-06-11 20:07 ` Romain Perier
2021-06-11 20:08 ` [PATCH v4 2/3] watchdog: Add Mstar MSC313e WDT driver Romain Perier
2021-06-11 20:08 ` Romain Perier
2021-06-11 20:08 ` [PATCH v4 3/3] ARM: dts: mstar: Add watchdog device_node definition Romain Perier
2021-06-11 20:08 ` Romain Perier
2021-06-12 12:59 ` [PATCH v4 0/3] Add watchdog for Mstar SoCs Guenter Roeck
2021-06-12 12:59 ` Guenter Roeck
2021-06-12 17:10 ` Daniel Palmer [this message]
2021-06-12 17:10 ` Daniel Palmer
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='CAFr9PX=j3UxbawtuvQnyoToH=3iT_k+j_LByUF-uDd0yDOk2ZQ@mail.gmail.com' \
--to=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mohammed.billoo@gmail.com \
--cc=robh+dt@kernel.org \
--cc=romain.perier@gmail.com \
--cc=wim@linux-watchdog.org \
/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.