From: Guenter Roeck <linux@roeck-us.net>
To: Florian Fainelli <f.fainelli@gmail.com>, linux-kernel@vger.kernel.org
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Rob Herring <robh+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"maintainer:BROADCOM BCM63XX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
Justin Chen <justinpopo6@gmail.com>,
"open list:WATCHDOG DEVICE DRIVERS"
<linux-watchdog@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:MIPS" <linux-mips@vger.kernel.org>,
"moderated list:BROADCOM BCM63XX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 0/7] Removal of bcm63xx-wdt
Date: Fri, 3 Dec 2021 12:24:09 -0800 [thread overview]
Message-ID: <e63401b1-b924-a08c-98dd-5ce8ba1a89c3@roeck-us.net> (raw)
In-Reply-To: <78c9c9f7-7e7c-abde-066a-240d642f3412@gmail.com>
On 12/3/21 12:07 PM, Florian Fainelli wrote:
> On 11/12/21 2:46 PM, Florian Fainelli wrote:
>> his patch series prepares the bcm7038_wdt driver to support its bcm63xx
>> counter part, updates the MIPS BCM63xx platform code to provide the
>> necessary information about the "periph" clock, and finally proceeds
>> with removing the bcm63xx_wdt altogether.
>>
>> This was only compiled tested as I did not have a readily available
>> BCM63xx system to test with.
>>
>> This should also help with adding support for BCM4908 which Rafal is
>> working on.
>>
>> Changes in v5:
>> - removed unnecessary "bcm7038-wdt" platform devtype
>> - added Rob's Reviewed-by tags to the 2 binding patches
>>
>> Changes in v4:
>> - fixed binding patch (Rob, Guenter)
>> - updated Kconfig description title to mention BCM63xx
>>
>> Changes in v3:
>>
>> - added Guenter's and Thomas' tags to patch 6
>> - added missing initialization of id_table
>> - use Rafal's latest binding patch
>>
>> Changes in v2:
>>
>> - added Guenter's Reviewed-by where given
>> - update binding patch to pass make dt_bindings_check (Rob)
>
> Are we good with this version? If so, could it be picked up so we have
> one less driver to care about, and we have one additional binding
> converted to YAML?
>
It is queued in my watchdog-next branch, so Wim will hopefully
pick it up either from there or from the mailing list.
Guenter
prev parent reply other threads:[~2021-12-03 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 22:46 [PATCH v5 0/7] Removal of bcm63xx-wdt Florian Fainelli
2021-11-12 22:46 ` [PATCH v5 1/7] dt-bindings: watchdog: convert Broadcom's WDT to the json-schema Florian Fainelli
2021-11-12 22:46 ` [PATCH v5 2/7] dt-bindings: watchdog: Add BCM6345 compatible to BCM7038 binding Florian Fainelli
2021-11-17 13:48 ` Guenter Roeck
2021-11-12 22:46 ` [PATCH v5 3/7] watchdog: bcm7038_wdt: Support platform data configuration Florian Fainelli
2021-11-12 22:46 ` [PATCH v5 4/7] watchdog: Allow building BCM7038_WDT for BCM63XX Florian Fainelli
2021-11-12 22:46 ` [PATCH v5 5/7] watchdog: bcm7038_wdt: Add platform device id for bcm63xx-wdt Florian Fainelli
2021-11-12 22:46 ` [PATCH v5 6/7] MIPS: BCM63XX: Provide platform data to watchdog device Florian Fainelli
2021-11-12 22:46 ` [PATCH v5 7/7] watchdog: Remove BCM63XX_WDT Florian Fainelli
2021-12-03 20:07 ` [PATCH v5 0/7] Removal of bcm63xx-wdt Florian Fainelli
2021-12-03 20:24 ` Guenter Roeck [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=e63401b1-b924-a08c-98dd-5ce8ba1a89c3@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=justinpopo6@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.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).