#!/bin/sh outfile="" now=`date +%s` while [ $# -gt 0 ] do case "$1" in -o) outfile="$2" shift 2;; -h) echo "usage: $0 [-o outfile] " exit 0;; *) break;; esac done if [ -z "$outfile" ] then outfile=`mktemp --tmpdir stackusage.$$.XXXX` fi KCFLAGS="${KCFLAGS} -fstack-usage" make "$@" # Prepend directory name to file names, remove column information, # make file:line/function/size/type properly tab-separated. find . -name '*.su' -newermt "@${now}" -print | \ xargs perl -MFile::Basename -pe \ '$d = dirname($ARGV); s#([^:]+:[0-9]+):[0-9]+:#$d/$1\t#;' | \ sort -k3,3nr > "${outfile}" echo "$0: output written to ${outfile}" 3f96b888f9a3cb For better readability, it is recommended to insert a newline before the 'status' property. Adjust the examples accordingly. Signed-off-by: David Heidelberg <david@ixit.cz> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://patch.msgid.link/20251023-docs-dt-newline-v1-1-1bf5e0040c0b@ixit.cz Signed-off-by: Rob Herring (Arm) <robh@kernel.org> docs: dt-bindings: Specify ordering for properties within groups 2025-03-21T16:27:56Z Dragan Simic dsimic@manjaro.org 2025-03-21T04:57:09Z urn:sha1:18d00558e89239e5c9a676341568b1ed6ecd4235 Ordering of the individual properties inside each property group benefits from applying natural sort order [1] by the property names, because it results in more logical and more usable property lists, similarly to what's already the case with the alpha-numerical ordering of the nodes without unit addresses. Let's have this clearly specified in the DTS coding style, and let's expand the provided node example a bit, to actually show the results of applying natural sort order. Applying strict alpha-numerical ordering can result in property lists that are suboptimal from the usability standpoint. For the provided example, which stems from a real-world DT, [2][3][4] applying strict alpha-numerical ordering produces the following undesirable result: vdd-0v9-supply = <&board_vreg1>; vdd-12v-supply = <&board_vreg3>; vdd-1v8-supply = <&board_vreg4>; vdd-3v3-supply = <&board_vreg2>; Having the properties sorted in natural order by their associated voltages is more logical, more usable, and a bit more consistent. [1] https://en.wikipedia.org/wiki/Natural_sort_order [2] https://lore.kernel.org/linux-rockchip/b39cfd7490d8194f053bf3971f13a43472d1769e.1740941097.git.dsimic@manjaro.org/ [3] https://lore.kernel.org/linux-rockchip/174104113599.8946.16805724674396090918.b4-ty@sntech.de/ [4] https://lore.kernel.org/linux-rockchip/757afa87255212dfa5abf4c0e31deb08@manjaro.org/ Signed-off-by: Dragan Simic <dsimic@manjaro.org> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://lore.kernel.org/r/6468619098f94d8acb00de0431c414c5fcfbbdbf.1742532899.git.dsimic@manjaro.org Signed-off-by: Rob Herring (Arm) <robh@kernel.org> docs: dt-bindings: Document preferred line wrapping 2025-01-23T22:53:10Z Krzysztof Kozlowski krzysztof.kozlowski@linaro.org 2025-01-18T10:22:47Z urn:sha1:1f744135f996257229f98c0ed3efc9726ac8c77f There are some patches with long lines as a result of checkpatch enforcing 100, not 80, but checkpatch is only a tool not a coding style. The Linux Kernel Coding Style is still clear here on preferred limit. Mentioned preferred style of wrapping long lines in DTS, based on Linux Kernel Coding Style. Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://lore.kernel.org/r/20250118102247.18257-1-krzysztof.kozlowski@linaro.org Signed-off-by: Rob Herring (Arm) <robh@kernel.org>