From: Guenter Roeck <linux@roeck-us.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "Lee Jones" <lee.jones@linaro.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Wim Van Sebroeck" <wim@linux-watchdog.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Justin Chen" <justinpopo6@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>,
"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH V4 RESEND 1/2] dt-bindings: watchdog: convert Broadcom's WDT to the json-schema
Date: Mon, 6 Dec 2021 11:51:15 -0800 [thread overview]
Message-ID: <20211206195115.GC3759192@roeck-us.net> (raw)
In-Reply-To: <46a88b40-6d92-727c-7adc-5723921d08e3@gmail.com>
On Mon, Dec 06, 2021 at 11:43:31AM -0800, Florian Fainelli wrote:
[ ... ]
> >
> > Your series includes the patch discussed here, and it is the first patch
> > of your series. The second patch in your series depends on it. Are you
> > telling me that I should drop those two patches from your series ?
>
> No, quite the contrary, I want you to keep the entire 7 patches that
> converted the bcm7038-wdt binding to YAML and get rid of the bcm63xx-wdt
> changes, the branch that you have right now is good in that regard.
>
> I don't see why you should be creating an immutable branch for Lee and
> not simply merge Rafal's "[PATCH V4 RESEND 2/2] dt-bindings: mfd: add
> Broadcom's Timer-Watchdog block" patch with Lee's ack directly. This is
> a new file, so I don't see how it would create conflicts as long as we
> don't pile up changes on top.
It sounded to me like Lee wanted an immutable branch for that, which I
can't do for watchdog. That means the options are to either drop the dt
changes, or to drop everything until after the dt issues are sorted out.
Guenter
next prev parent reply other threads:[~2021-12-06 19:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 5:53 [PATCH V4 RESEND 1/2] dt-bindings: watchdog: convert Broadcom's WDT to the json-schema Rafał Miłecki
2021-11-15 5:53 ` [PATCH V4 RESEND 2/2] dt-bindings: mfd: add Broadcom's Timer-Watchdog block Rafał Miłecki
2021-11-18 22:45 ` Rob Herring
2021-12-29 9:44 ` Lee Jones
2021-12-06 7:50 ` [PATCH V4 RESEND 1/2] dt-bindings: watchdog: convert Broadcom's WDT to the json-schema Rafał Miłecki
2021-12-06 8:44 ` Lee Jones
2021-12-06 8:53 ` Rafał Miłecki
2021-12-06 9:05 ` Lee Jones
2021-12-06 17:20 ` Florian Fainelli
2021-12-06 18:55 ` Lee Jones
2021-12-06 19:10 ` Guenter Roeck
2021-12-06 19:13 ` Florian Fainelli
2021-12-06 19:37 ` Guenter Roeck
2021-12-06 19:43 ` Florian Fainelli
2021-12-06 19:51 ` Guenter Roeck [this message]
2021-12-07 10:03 ` Lee Jones
2021-12-07 15:29 ` Guenter Roeck
2021-12-07 15:44 ` Lee Jones
2021-12-28 9:21 ` Wim Van Sebroeck
2021-12-29 9:45 ` Lee Jones
2021-12-06 21:14 ` Rafał Miłecki
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=20211206195115.GC3759192@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=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=zajec5@gmail.com \
/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).