linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Lee Jones" <lee.jones@linaro.org>, "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Wim Van Sebroeck" <wim@linux-watchdog.org>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"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 09:20:01 -0800	[thread overview]
Message-ID: <f5745952-9e3c-ed7a-cced-ce42d3da2276@gmail.com> (raw)
In-Reply-To: <Ya3SU6U6YT6mlFu8@google.com>

On 12/6/21 1:05 AM, Lee Jones wrote:
> On Mon, 06 Dec 2021, Rafał Miłecki wrote:
> 
>> On 06.12.2021 09:44, Lee Jones wrote:
>>> On Mon, 06 Dec 2021, Rafał Miłecki wrote:
>>>> On 15.11.2021 06:53, Rafał Miłecki wrote:
>>>>> From: Rafał Miłecki <rafal@milecki.pl>
>>>>>
>>>>> This helps validating DTS files.
>>>>>
>>>>> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
>>>>> Acked-by: Florian Fainelli <f.fainelli@gmail.com>
>>>>> Reviewed-by: Rob Herring <robh@kernel.org>
>>>>
>>>> I'm not familiar with handling multi-subsystem patchsets (here: watchdog
>>>> & MFD).
>>>>
>>>> Please kindly let me know: how to proceed with this patchset now to get
>>>> it queued for Linus?
>>>
>>> What is the requirement for these to be merged together?
>>
>> If you merge 2/2 without 1/2 then people running "make dt_binding_check"
>> may see 1 extra warning until both patches meet in Linus's tree.
>>
>> So it all comes to how much you care about amount of warnings produced
>> by "dt_binding_check".
> 
> In -next, I don't, but I know Rob gets excited about it.
> 
> Rob, what is your final word on this?  Is it a forced requirement for
> all interconnected document changes to go in together?

The first patch is queued up in Guenter's watchdog tree here:

https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/commit/?h=watchdog-next&id=a5b2ebc8f6e67b5c81023e8bde6b19ff48ffdb02

and will be submitted to Wim shortly I believe, so I suppose we should
take patch #2 via Guenter and Wim's tree as well logically.
-- 
Florian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-12-06 17:21 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 [this message]
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
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=f5745952-9e3c-ed7a-cced-ce42d3da2276@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --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=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).