From: Guenter Roeck <linux@roeck-us.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [RESEND PATCH v3 0/3] watchdog: f71808e_wdt: migrate to new kernel API
Date: Mon, 3 May 2021 06:33:21 -0700 [thread overview]
Message-ID: <9b24f6de-c989-8055-25d7-518ff6cc3393@roeck-us.net> (raw)
In-Reply-To: <20210503130948.y7w6a2wbonr6zxzu@pengutronix.de>
On 5/3/21 6:09 AM, Marc Kleine-Budde wrote:
> On 13.04.2021 12:46:43, Ahmad Fatoum wrote:
>> This series migrates the driver to the new kernel watchdog API and
>> then to the driver model.
>>
>> Main feedback from Guenther on v2 was that I need to split it up to
>> enable review. I have done so by removing the extra refactoring for
>> now and focused on the functional changes described above. The diff
>> is now much better readable.
>>
>> I tested it on a f81866.
>
> Is there a chance to get this series applied and mainline? Is there
> anything that's blocking it?
>
Yes, time to review. Sorry, I am way backlogged with code reviews.
Guenter
next prev parent reply other threads:[~2021-05-03 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 10:46 [RESEND PATCH v3 0/3] watchdog: f71808e_wdt: migrate to new kernel API Ahmad Fatoum
2021-04-13 10:46 ` [RESEND PATCH v3 1/3] watchdog: f71808e_wdt: rename variant-independent identifiers appropriately Ahmad Fatoum
2021-04-13 10:46 ` [RESEND PATCH v3 2/3] watchdog: f71808e_wdt: migrate to new kernel watchdog API Ahmad Fatoum
2021-05-03 14:31 ` Guenter Roeck
2021-05-03 14:39 ` Ahmad Fatoum
2021-05-03 15:28 ` Guenter Roeck
2021-05-03 18:33 ` Ahmad Fatoum
2021-04-13 10:46 ` [RESEND PATCH v3 3/3] watchdog: f71808e_wdt: refactor to platform device/driver pair Ahmad Fatoum
2021-05-03 13:09 ` [RESEND PATCH v3 0/3] watchdog: f71808e_wdt: migrate to new kernel API Marc Kleine-Budde
2021-05-03 13:33 ` Guenter Roeck [this message]
2021-05-03 13:49 ` Marc Kleine-Budde
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=9b24f6de-c989-8055-25d7-518ff6cc3393@roeck-us.net \
--to=linux@roeck-us.net \
--cc=a.fatoum@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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).