lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9e36d2353aadb293ee277329eed84c4015bc0277.camel@mediatek.com>
Date:   Wed, 27 Oct 2021 10:27:45 +0800
From:   Tinghan Shen <tinghan.shen@...iatek.com>
To:     Rob Herring <robh@...nel.org>
CC:     AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>,
        "Benson Leung" <bleung@...omium.org>,
        <Project_Global_Chrome_Upstream_Group@...iatek.com>,
        <linux-mediatek@...ts.infradead.org>,
        Lee Jones <lee.jones@...aro.org>,
        "Enric Balletbo i Serra" <enric.balletbo@...labora.com>,
        Rob Herring <robh+dt@...nel.org>,
        Matthias Brugger <matthias.bgg@...il.com>,
        "Guenter Roeck" <groeck@...omium.org>, <devicetree@...r.kernel.org>
Subject: Re: [PATCH] dt-bindings: mfd: change naming of mediatek rpmsg
 property

On Mon, 2021-10-18 at 12:32 -0500, Rob Herring wrote:
> On Mon, 18 Oct 2021 19:51:11 +0800, Tinghan Shen wrote:
> > Change from "mtk,rpmsg-name" to "mediatek,rpmsg-name" to sync with
> > the
> > vendor name defined in vendor-prefixes.yaml.
> > 
> > Signed-off-by: Tinghan Shen <tinghan.shen@...iatek.com>
> > ---
> >  Documentation/devicetree/bindings/mfd/google,cros-ec.yaml | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> 
> Running 'make dtbs_check' with the schema in this patch gives the
> following warnings. Consider if they are expected or the schema is
> incorrect. These may not be new warnings.
> 
> Note that it is not yet a requirement to have 0 warnings for
> dtbs_check.
> This will change in the future.
> 
> Full log is available here: 
> https://urldefense.com/v3/__https://patchwork.ozlabs.org/patch/1542563__;!!CTRNKA9wMg0ARbw!yQGrJgf_q0cFKm4GiKGqWF4eFuMbBE3w_p4r9ipndPFZMOYDBfs0oAwGpZa6mKdIggI$
>  
> 
> 
> cros_ec: 'mtk,rpmsg-name' does not match any of the regexes:
> '^extcon[0-9]*$', '^i2c-tunnel[0-9]*$', '^regulator@[0-9]+$',
> 'pinctrl-[0-9]+'
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-
> burnet.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-damu.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-
> fennel14.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-fennel-
> sku1.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-fennel-
> sku6.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-juniper-
> sku16.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-kappa.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-kenzo.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-willow-
> sku0.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-willow-
> sku1.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-kakadu.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-kodama-sku16.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-kodama-sku272.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-kodama-sku288.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-kodama-sku32.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-krane-sku0.dt.yaml
> 	arch/arm64/boot/dts/mediatek/mt8183-kukui-krane-sku176.dt.yaml
> 

Hi Rob,

Thanks for your reviewing. I'm sorry that forget to mention the
dependency of this patch.

This patch is introduced because of this change,

https://lore.kernel.org/all/20210924033935.2127-7-tinghan.shen@mediatek.com/

I will resend this patch to mention the dependency.

Best regards,
TingHan


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ