Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp1163336ybm; Sat, 30 May 2020 00:20:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzaScxRn5oM/fv7LpoKUJyb9cqin3WMVBtdyAbmwb/w1BeDEd5XjGlNRB44cqAFR64s8hDU X-Received: by 2002:a17:906:d8d7:: with SMTP id re23mr10444048ejb.22.1590823217291; Sat, 30 May 2020 00:20:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590823217; cv=none; d=google.com; s=arc-20160816; b=StJbEc1W2kgV5AEq2NDy8lNXrKu1MtrGlvCvAx8Gq8jnar8SqtLaq6pKOYVUw/SiHs EttPAtJmndKSDw7dFGLuAKLkI05pvxH9R3qFrr2gPuEf04WKW/arYJYqHuTcp8uIheNO 7DMtH1Vl041hr2pXiuBPQPzj5O2pOdnl+9L/GeRzvIJCwlhiDD3ZKtABtHsfZUYRTg2N WcsVhpV8iX58r8/jig5eZs8oCPi++e25I7Y0N+3hBuIeq0q88Nn4m+SaIpMArIRD8HqN +Pyr1dA3dGYeGdKl5boZEgjOgepGwV8/e2FoX0x9ug9SaTrHavZ6XxCFheCIrrZmktRW N52g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:subject:cc:to:from:date:dkim-signature; bh=WVWuUrcR7m6UnSkPjLSxuCsO0z+r+giJUIU3u8iQGQ0=; b=fT2idtqj8Hcg6ei+HoqIpRfSobQJeFtaT2QHb6a2DrS5aH/3faeSiomDRMX9jYLKcN jjPJCAY+YY2u7dUyHKKUKmpt1vRDvJK1tW34F0KRbVEB//2RomP0tZflCRsZvAkjDpLD 5xXSDQLtvZeqvlerlsIWKfY1XdvOBqwx8J1dtkUrKL7P+lPH/yP+NQfvlWdBNnX24OZi T7KcqWg9w40n3mIckdanoSoXzbDp4+ILhkTr//HrZ5prTzTrlQgGto83U53DK+vvl2wG utEGQvZOWnpjRSg8naqS8UUrgYM6lvHxiarRkdnQeQJJqoqzVD9wFp1Bd1PV82w3bhlk YXfw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@flygoat.com header.s=vultr header.b=mhLNh75T; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=flygoat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a9si6818895edt.564.2020.05.30.00.19.53; Sat, 30 May 2020 00:20:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@flygoat.com header.s=vultr header.b=mhLNh75T; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=flygoat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728807AbgE3HSF (ORCPT + 99 others); Sat, 30 May 2020 03:18:05 -0400 Received: from vultr.net.flygoat.com ([149.28.68.211]:34790 "EHLO vultr.net.flygoat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728714AbgE3HSF (ORCPT ); Sat, 30 May 2020 03:18:05 -0400 Received: from halation.net.flygoat.com (unknown [IPv6:240e:390:496:b320::d68]) by vultr.net.flygoat.com (Postfix) with ESMTPSA id 9020420E8D; Sat, 30 May 2020 07:17:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=flygoat.com; s=vultr; t=1590823084; bh=FokPmXVAmxcnVPTY1hKOBLr9DbGlwiipDcqx7CnsyLs=; h=Date:From:To:Cc:Subject:From; b=mhLNh75TUpn2Ry6HuI0nCWnGDcXsCtjZvU9iJwuuP3hwMpgEJgb8m/EmIGLKwHaN7 c1bgvQ87OxVojzF80t3wt41pou3sWnoUdc3twFKwGWedF0oBmL1wv8CJ3WwNS0KEze kYILkyIaH9hwcLAsMKpGqCMBuC6EqJJSIT/zeiD3zOG1pw9NqFFMoZC/kEJsP8CNsV REjf+NFhvCr6qHuSxoyVr4uEK1hm+skhNe1Q+nq+YerLF9U1mxGd583VcfDnEW3Jo5 b3x4sgysP/pQ6H/hbnMrkopI8QbimuCYbVb1OAxXh1DuTfpFjmYbrFDr4Oz75gssuo X2++150GGBReA== Date: Sat, 30 May 2020 15:17:52 +0800 From: Jiaxun Yang To: robh@kernel.org Cc: apw@canonical.com, joe@perches.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: checkpatch warnings with PCI DT compatible string Message-ID: <20200530151752.2f40fb08@halation.net.flygoat.com> X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi there, When I was trying to create dts for my platform that need PCI DeviceTree sub node to express interrupt of children devices under the bridge, like this: pci@1a000000 { compatible = "loongson,ls7a-pci"; device_type = "pci"; #address-cells = <3>; #size-cells = <2>; #interrupt-cells = <2>; msi-parent = <&msi>; reg = <0 0x1a000000 0 0x02000000>, <0xefe 0x00000000 0 0x20000000>; ranges = <0x01000000 0x0 0x00020000 0x0 0x00020000 0x0 0x00020000>, <0x02000000 0x0 0x40000000 0x0 0x40000000 0x0 0x40000000>; ohci@4,0 { compatible = "pci0014,7a24.0", "pci0014,7a24", "pciclass0c0310", "pciclass0c03"; reg = <0x2000 0x0 0x0 0x0 0x0>; interrupts = <49 IRQ_TYPE_LEVEL_HIGH>; interrupt-parent = <&pic>; }; }; I got such checkpatch warnings: WARNING: DT compatible string "pci0014,7a24.0" appears un-documented -- check ./Documentation/devicetree/bindings/ #206: FILE: arch/mips/boot/dts/loongson/ls7a-pch.dtsi:38: + compatible = "pci0014,7a24.0", WARNING: DT compatible string vendor "pci0014" appears un-documented -- check ./Documentation/devicetree/bindings/vendor-prefixes.yaml #206: FILE: arch/mips/boot/dts/loongson/ls7a-pch.dtsi:38: + compatible = "pci0014,7a24.0", Just wonder if using such compatible string is allowed? I've saw some some usages like mine in the tree, such as arch/x86/platform/ce4100/falconfalls.dts, and arch/mips/boot/dts/img/boston.dts. If that's allowed, should we surpress these warnings in checkpatch script? Thanks. -- Jiaxun Yang