From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2FF4DC433FE for ; Fri, 15 Oct 2021 22:03:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1235161181 for ; Fri, 15 Oct 2021 22:03:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232796AbhJOWFn (ORCPT ); Fri, 15 Oct 2021 18:05:43 -0400 Received: from mail.kernel.org ([198.145.29.99]:54970 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235521AbhJOWFm (ORCPT ); Fri, 15 Oct 2021 18:05:42 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 5D83761163; Fri, 15 Oct 2021 22:03:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1634335415; bh=C+8ImSjOE4e/oErYg2vp5sosCuJhm/T5ZYTjwR9eR/w=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=Vbyc5NQenlvVHhDUrIqPcPRWgRIhUFUxhg0gwOjbTIgtxUYq0QeuRXpLgVYOiRn7V gp/KDQlNeLPkNSHcO2dGvX99ltXzy11lWO99rMGAh2Ft28TTbI/7klAtfi3y3NxDJB p8uANg+Gz4XNDU2Vidawg+FIuVvPgYNxHsCuke6MFZHBdXxB2RcZR2fWAPRuA7RUae stOSwN15C2W3dcif8SbXjaKXKoZwhpMRpP58THRO9MiaOoAFpX+mID0+bpco3ImhVU Tn+cFvD/ool/xjMdtk/r4SnRd1oKeZAKPjD8PtgvlpO9PNF7bPd8xysIg8qeypCiiW eB6PuuGAHQ9Pw== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <20210923064137.60722-1-zhang.lyra@gmail.com> <163425256290.1688384.5646232860050218479@swboyd.mtv.corp.google.com> Subject: Re: [PATCH v4 2/4] dt-bindings: mfd: sprd: Add bindings for ums512 global registers From: Stephen Boyd Cc: Lee Jones , Chunyan Zhang , linux-clk , OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS , Baolin Wang , Orson Zhai , Chunyan Zhang , LKML To: Geert Uytterhoeven , Rob Herring Date: Fri, 15 Oct 2021 15:03:34 -0700 Message-ID: <163433541408.1688384.16269113818432626325@swboyd.mtv.corp.google.com> User-Agent: alot/0.9.1 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Geert Uytterhoeven (2021-10-15 10:09:10) > Hi Rob, Stephen, >=20 > On Fri, Oct 15, 2021 at 3:59 PM Rob Herring wrote: > > On Thu, Oct 14, 2021 at 6:02 PM Stephen Boyd wrote: > > > Quoting Rob Herring (2021-10-14 09:18:16) > > > > On Thu, Oct 14, 2021 at 1:48 AM Lee Jones wr= ote: > > > > > > > > > > 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 beca= use > > > > 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=3D""`= but > > > nowadays this seems to check all the bindings and not just the one > > > binding I care to check. Did something break? > > > > It should apply all the schemas to the example in DT_SCHEMA_FILES. > > Originally, it only applied DT_SCHEMA_FILES schema to the example in > > DT_SCHEMA_FILES. >=20 > Probably Stephen means that yamllint is still run on all files, which > I tried to fix in [1]? >=20 > I've been running an improved version for months, but I haven't sent > it out yet. >=20 Oh yeah probably. Do I need to carry this patch locally until it is fixed?