From: Mark Balantzyan <mbalant3@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Mark Balantzyan <mbalant3@gmail.com>,
wim@linux-watchdog.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org, andrianov@ispras.ru
Subject: Re: [PATCH 1/4] watchdog device drivers:pc87413_wdt:Rewriting of pc87413_wdt driver to utilize common watchdog interface
Date: Mon, 29 Jul 2019 19:47:54 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1907291947330.103354@mbalantz-desktop> (raw)
In-Reply-To: <792afc6c-f705-a048-4e6d-81d00754c0ea@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
Yes, each time I go through an edit I discover something I missed,
apologies. Will be working on it for a bit, currently getting compile time
errors. Just letting you know and it’s good we’re checking :-)
Thank you,
Mark
prev parent reply other threads:[~2019-07-30 2:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 2:15 [PATCH 1/4] watchdog device drivers:pc87413_wdt:Rewriting of pc87413_wdt driver to utilize common watchdog interface Mark Balantzyan
2019-07-30 2:15 ` [PATCH 2/4] watchdog device drivers:pc87413_wdt:Rewriting of pc87413_wdt driver to utilize common watchdog interface, with removal of file access functions for correct functionality Mark Balantzyan
2019-07-30 2:15 ` [PATCH 3/4] watchdog device drivers:pc87413_wdt: Tidying up conversion of pc87413_wdt driver to common watchdog interface, removal of some stray nowayout parameters Mark Balantzyan
2019-07-30 2:35 ` Guenter Roeck
2019-07-30 2:15 ` [PATCH 4/4] watchdog device drivers:pc87413_wdt: Continuing revision of conversion of pc87413_wdt to use common watchdog interface, removed undeclared identifiers Mark Balantzyan
2019-07-30 2:28 ` Guenter Roeck
2019-07-30 2:33 ` [PATCH 1/4] watchdog device drivers:pc87413_wdt:Rewriting of pc87413_wdt driver to utilize common watchdog interface Guenter Roeck
2019-07-30 2:38 ` Guenter Roeck
2019-07-30 2:47 ` Mark Balantzyan [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=alpine.DEB.2.21.1907291947330.103354@mbalantz-desktop \
--to=mbalant3@gmail.com \
--cc=andrianov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).