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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 6 Dec 2020 13:18:31 +0800 From: "Leizhen (ThunderTown)" <thunder.leizhen@...wei.com> To: Mark Brown <broonie@...nel.org> CC: Rob Herring <robh+dt@...nel.org>, Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>, Shawn Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, "Pengutronix Kernel Team" <kernel@...gutronix.de>, Fabio Estevam <festevam@...il.com>, "NXP Linux Team" <linux-imx@....com>, David Airlie <airlied@...ux.ie>, "Daniel Vetter" <daniel@...ll.ch>, Sumit Semwal <sumit.semwal@...aro.org>, "Thierry Reding" <thierry.reding@...il.com>, Sam Ravnborg <sam@...nborg.org>, "Hans Verkuil" <hverkuil-cisco@...all.nl>, Mauro Carvalho Chehab <mchehab@...nel.org>, Sakari Ailus <sakari.ailus@...ux.intel.com>, "Ricardo Ribalda" <ribalda@...nel.org>, Ulf Hansson <ulf.hansson@...aro.org>, "Matthias Brugger" <matthias.bgg@...il.com>, Liam Girdwood <lgirdwood@...il.com>, linux-clk <linux-clk@...r.kernel.org>, devicetree <devicetree@...r.kernel.org>, linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>, linux-kernel <linux-kernel@...r.kernel.org>, dri-devel <dri-devel@...ts.freedesktop.org>, linux-media <linux-media@...r.kernel.org>, linux-mmc <linux-mmc@...r.kernel.org>, linux-mediatek <linux-mediatek@...ts.infradead.org>, alsa-devel <alsa-devel@...a-project.org> Subject: Re: [PATCH 1/1] dt-bindings: eliminate yamllint warnings On 2020/12/5 1:41, Mark Brown wrote: > On Fri, Dec 04, 2020 at 10:42:26AM +0800, Zhen Lei wrote: >> All warnings are related only to "wrong indentation", except one: >> Documentation/devicetree/bindings/media/i2c/mipi-ccs.yaml:4:1: \ >> [error] missing document start "---" (document-start) > > It would make life easier (and be more normal practice) to split this up > by driver/subsystem and send a bunch of separate patches to the relevant > maintainers, this makes it much easier to review and handle things. Okay, I'll split this patch and send them separately. I'm not going to mark the new patches as v2 to save trouble. >
Powered by blists - more mailing lists