From: Wim Van Sebroeck <wim@linux-watchdog.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: "Guenter Roeck" <linux@roeck-us.net>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"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: Tue, 28 Dec 2021 10:21:40 +0100 [thread overview]
Message-ID: <20211228092140.GA26632@www.linux-watchdog.org> (raw)
In-Reply-To: <Ya+BX1X7/YqmfCU8@google.com>
Hi Lee,
> On Tue, 07 Dec 2021, Guenter Roeck wrote:
>
> > On 12/7/21 2:03 AM, Lee Jones wrote:
> > [ ... ]
> > > > It sounded to me like Lee wanted an immutable branch for that
> > >
> > > Not exactly, I said:
> > >
> > > "> Suppose we should take patch #2 via [Watchdog] as well.
> > >
> > > If that happens, I would like a PR to an immutable branch."
> > >
> > > The alternative is that I take the patch and provide an immutable
> > > branch to you, which I am in a position to do.
> > >
> >
> > I understand, only I am not in a position to take it since my tree
> > isn't the official watchdog-next tree, and it doesn't show up in -next.
> > If Wim takes it into the official watchdog-next tree or not would be
> > completely up to him.
> >
> > I personally don't care if the bindings check is clean in my inofficial
> > tree, so maybe this is a non-issue.
>
> That doesn't help, sadly.
>
> I think the best course of action is for Wim to let me know when this
> patch makes it into his tree. I'll take the MFD one at the same time
> and the two shall meet in -next.
>
> Honestly, this is all such a faff.
>
> Just to keep a script happy that 3 people care about.
It's going in today.
Kind regards,
Wim.
next prev parent reply other threads:[~2021-12-28 10:58 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
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 [this message]
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=20211228092140.GA26632@www.linux-watchdog.org \
--to=wim@linux-watchdog.org \
--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=linux@roeck-us.net \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.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).