From: Stephen Boyd <sboyd@kernel.org>
To: Lee Jones <lee.jones@linaro.org>, Rob Herring <robh+dt@kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Chunyan Zhang <zhang.lyra@gmail.com>,
linux-clk <linux-clk@vger.kernel.org>,
open list: OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
<devicetree@vger.kernel.org>,
Baolin Wang <baolin.wang7@gmail.com>,
Orson Zhai <orsonzhai@gmail.com>,
Chunyan Zhang <chunyan.zhang@unisoc.com>,
LKML <linux-kernel@vger.kernel.org>, ;
Subject: Re: [PATCH v4 2/4] dt-bindings: mfd: sprd: Add bindings for ums512 global registers
Date: Thu, 14 Oct 2021 16:02:42 -0700 [thread overview]
Message-ID: <163425256290.1688384.5646232860050218479@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <CAL_Jsq+GHt+DqHa0GeLKWoni+Lghg5wg5ssREZBdSD-=K3XQ1A@mail.gmail.com>
Quoting Rob Herring (2021-10-14 09:18:16)
> On Thu, Oct 14, 2021 at 1:48 AM Lee Jones <lee.jones@linaro.org> wrote:
> >
> > I don't explicitly build DT documentation.
> >
> > Since I use the build bots to let me know if there are strange !(C,
> > ASM, arm, aarch64, mips, ppc, x86) build issues or ones with odd
> > configuration possibilities (randconfig) in the repos I maintain, you
> > might have to convince them that this is important too.
>
> It's really just a matter of turning on the build in
> allyesconfig/allmodconfig builds. I've not done that primarily because
> there's one person I don't want to yell at me, but I could probably
> make it arm and/or arm64 only. It's really arch and config
> independent, so doing it multiple times is kind of pointless.
>
> I assume for bots you mean kernel-ci mainly? Do you run that before
> stuff gets into linux-next? IMO, that's too late. But still a slight
> improvement if things go in via one tree. Otherwise, I see the
> breakage twice, 1st linux-next then the merge window.
>
I run `make dt_binding_check DT_SCHEMA_FILES="<path to yaml file>"` but
nowadays this seems to check all the bindings and not just the one
binding I care to check. Did something break?
next prev parent reply other threads:[~2021-10-14 23:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 6:41 [PATCH v4 0/4] Add Unisoc's UMS512 clock support Chunyan Zhang
2021-09-23 6:41 ` [PATCH v4 1/4] dt-bindings: clk: sprd: Add bindings for ums512 clock controller Chunyan Zhang
2021-09-27 19:48 ` Rob Herring
2021-10-13 14:22 ` Geert Uytterhoeven
2021-10-16 8:41 ` Chunyan Zhang
2021-10-17 12:29 ` Geert Uytterhoeven
2021-09-23 6:41 ` [PATCH v4 2/4] dt-bindings: mfd: sprd: Add bindings for ums512 global registers Chunyan Zhang
2021-10-06 8:00 ` Lee Jones
2021-10-11 14:11 ` Rob Herring
2021-10-12 8:14 ` Lee Jones
2021-10-13 14:23 ` Geert Uytterhoeven
2021-10-14 6:48 ` Lee Jones
2021-10-14 16:18 ` Rob Herring
2021-10-14 23:02 ` Stephen Boyd [this message]
2021-10-15 13:58 ` Rob Herring
2021-10-15 17:09 ` Geert Uytterhoeven
2021-10-15 22:03 ` Stephen Boyd
2021-10-18 11:37 ` Geert Uytterhoeven
2021-10-15 12:45 ` Lee Jones
2021-10-15 17:11 ` Rob Herring
2021-10-18 11:53 ` Lee Jones
2021-10-20 15:09 ` Rob Herring
2021-10-20 15:58 ` Lee Jones
2021-10-13 22:04 ` Stephen Boyd
2021-10-13 23:49 ` ChunyanZhang
2021-10-14 1:51 ` Stephen Boyd
2021-10-14 2:02 ` ChunyanZhang
2021-10-14 6:38 ` Stephen Boyd
2021-10-14 8:18 ` ChunyanZhang
2021-10-14 23:09 ` Stephen Boyd
2021-09-23 6:41 ` [PATCH v4 3/4] clk: sprd: Add dt-bindings include file for UMS512 Chunyan Zhang
2021-09-27 19:49 ` Rob Herring
2021-09-23 6:41 ` [PATCH v4 4/4] clk: sprd: Add Unisoc's UMS512 clock driver Chunyan Zhang
2021-10-12 12:09 ` Re:[PATCH v4 0/4] Add Unisoc's UMS512 clock support ChunyanZhang
2022-04-27 10:08 [PATCH V4 0/4] Add ums512 clocks and relative bindings file Cixi Geng
2022-04-27 10:08 ` [PATCH V4 2/4] dt-bindings: mfd: sprd: Add bindings for ums512 global registers Cixi Geng
2022-05-03 19:28 ` Rob Herring
2022-05-04 15:12 ` Krzysztof Kozlowski
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=163425256290.1688384.5646232860050218479@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=baolin.wang7@gmail.com \
--cc=chunyan.zhang@unisoc.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=lee.jones@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=robh+dt@kernel.org \
--cc=zhang.lyra@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).