From: Rob Herring <robh@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Corey Minyard <minyard@acm.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 13
Date: Wed, 13 Oct 2021 07:13:09 -0500 [thread overview]
Message-ID: <YWbNVXemcnxO8wsG@robh.at.kernel.org> (raw)
In-Reply-To: <20211013170522.4c6e21a1@canb.auug.org.au>
On Wed, Oct 13, 2021 at 05:05:22PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next release tomorrow.
>
> Changes since 20211012:
>
> The arm-soc tree lost its build failure.
>
> The net-next tree gained a conflict against the net tree.
>
> The drm-misc tree lost its build failure.
>
> The amdgpu tree lost its build failure.
>
> Non-merge commits (relative to Linus' tree): 7055
> 6867 files changed, 394074 insertions(+), 162696 deletions(-)
The commit 9cc6726f68af ("ipmi:ipmb: Add OF support") was added and has
warnings for 'make dt_binding_check'. I'm replying here because the
commit hasn't been sent to any list in lore.
Documentation/devicetree/bindings/ipmi/ipmi-ipmb.example.dts:22.13-26: Warning (reg_format): /example-0/ipmi-ipmb@0x40:reg: property has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1)
Documentation/devicetree/bindings/ipmi/ipmi-ipmb.example.dts:19.24-26.11: Warning (unit_address_format): /example-0/ipmi-ipmb@0x40: unit name should not have leading "0x"
Documentation/devicetree/bindings/ipmi/ipmi-ipmb.example.dt.yaml: Warning (pci_device_reg): Failed prerequisite 'reg_format'
Documentation/devicetree/bindings/ipmi/ipmi-ipmb.example.dt.yaml: Warning (pci_device_bus_num): Failed prerequisite 'reg_format'
Documentation/devicetree/bindings/ipmi/ipmi-ipmb.example.dt.yaml: Warning (simple_bus_reg): Failed prerequisite 'reg_format'
Documentation/devicetree/bindings/ipmi/ipmi-ipmb.example.dt.yaml: Warning (i2c_bus_reg): Failed prerequisite 'reg_format'
Documentation/devicetree/bindings/ipmi/ipmi-ipmb.example.dt.yaml: Warning (spi_bus_reg): Failed prerequisite 'reg_format'
/builds/robherring/linux-dt/Documentation/devicetree/bindings/ipmi/ipmi-ipmb.example.dt.yaml: example-0: ipmi-ipmb@0x40:reg:0: [64] is too short
From schema: /usr/local/lib/python3.8/dist-packages/dtschema/schemas/reg.yaml
/builds/robherring/linux-dt/Documentation/devicetree/bindings/ipmi/ipmi-ipmb.example.dt.yaml: example-0: 'ipmi-ipmb@0x40' does not match any of the regexes: '.*-names$', '.*-supply$', '^#.*-cells$', '^#[a-zA-Z0-9,+\\-._]{0,63}$', '^[a-zA-Z][a-zA-Z0-9,+\\-._]{0,63}$', '^[a-zA-Z][a-zA-Z0-9,+\\-._]{0,63}@[0-9a-fA-F]+(,[0-9a-fA-F]+)*$', '^__.*__$', 'pinctrl-[0-9]+'
From schema: /usr/local/lib/python3.8/dist-packages/dtschema/schemas/dt-core.yaml
Rob
next prev parent reply other threads:[~2021-10-13 12:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 6:05 linux-next: Tree for Oct 13 Stephen Rothwell
2021-10-13 12:13 ` Rob Herring [this message]
2021-10-13 13:50 ` Corey Minyard
2021-10-13 14:47 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2023-10-13 5:55 Stephen Rothwell
2022-10-13 2:49 Stephen Rothwell
2020-10-13 8:04 Stephen Rothwell
2016-10-13 2:31 Stephen Rothwell
2015-10-13 7:15 Stephen Rothwell
2014-10-13 4:33 Stephen Rothwell
2014-10-13 5:37 ` Stephen Rothwell
2011-10-13 7:16 Stephen Rothwell
2011-10-13 9:38 ` Sedat Dilek
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=YWbNVXemcnxO8wsG@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=minyard@acm.org \
--cc=sfr@canb.auug.org.au \
/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).