From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: wim@linux-watchdog.org, linux@roeck-us.net
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH v2 0/2] watchdog: f71808e_wdt: migrate to new kernel API
Date: Tue, 20 Oct 2020 08:21:10 +0200 [thread overview]
Message-ID: <20201020062112.6762-1-a.fatoum@pengutronix.de> (raw)
This series migrates the driver to use first the driver model, then
the new kernel watchdog API.
I tested it on a f81866.
v1 had a wrong title (f71808e_wdt: migrate to kernel). It's available here:
https://lore.kernel.org/linux-watchdog/20200611191750.28096-1-a.fatoum@pengutronix.de/
v1 -> v2:
- reworked to platform device/driver pair (Guenther)
- squashed identifier renaming into the patches that touch
the respective lines anyway
- fixed checkpatch.pl nitpicks (Guenther)
- fixed locally used variable declared without static (0-day)
- fixed unneded line break due to old line limit (Guenther)
- renamed struct fintek_wdog_data to struct fintek_wdt
Ahmad Fatoum (2):
watchdog: f71808e_wdt: refactor to platform device/driver pair
watchdog: f71808e_wdt: migrate to new kernel watchdog API
drivers/watchdog/Kconfig | 1 +
drivers/watchdog/f71808e_wdt.c | 815 ++++++++++++---------------------
2 files changed, 292 insertions(+), 524 deletions(-)
--
2.28.0
next reply other threads:[~2020-10-20 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 6:21 Ahmad Fatoum [this message]
2020-10-20 6:21 ` [PATCH v2 1/2] watchdog: f71808e_wdt: refactor to platform device/driver pair Ahmad Fatoum
2020-11-08 17:26 ` Guenter Roeck
2020-11-17 11:01 ` Ahmad Fatoum
2020-10-20 6:21 ` [PATCH v2 2/2] watchdog: f71808e_wdt: migrate to new kernel watchdog API Ahmad Fatoum
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=20201020062112.6762-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=kernel@pengutronix.de \
--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).