diff options
author | Jack Rosenthal <jrosenth@chromium.org> | 2021-11-04 12:11:58 -0600 |
---|---|---|
committer | Commit Bot <commit-bot@chromium.org> | 2021-11-05 04:22:34 +0000 |
commit | 252457d4b21f46889eebad61d4c0a65331919cec (patch) | |
tree | 01856c4d31d710b20e85a74c8d7b5836e35c3b98 /util/check_allowed.sh | |
parent | 08f5a1e6fc2c9467230444ac9b582dcf4d9f0068 (diff) | |
download | chrome-ec-stabilize-14469.9.B-ish.tar.gz |
ish: Trim down the release branchstabilize-wristpin-14469.59.B-ishstabilize-voshyr-14637.B-ishstabilize-quickfix-14695.187.B-ishstabilize-quickfix-14695.124.B-ishstabilize-quickfix-14526.91.B-ishstabilize-14695.85.B-ishstabilize-14695.107.B-ishstabilize-14682.B-ishstabilize-14633.B-ishstabilize-14616.B-ishstabilize-14589.B-ishstabilize-14588.98.B-ishstabilize-14588.14.B-ishstabilize-14588.123.B-ishstabilize-14536.B-ishstabilize-14532.B-ishstabilize-14528.B-ishstabilize-14526.89.B-ishstabilize-14526.84.B-ishstabilize-14526.73.B-ishstabilize-14526.67.B-ishstabilize-14526.57.B-ishstabilize-14498.B-ishstabilize-14496.B-ishstabilize-14477.B-ishstabilize-14469.9.B-ishstabilize-14469.8.B-ishstabilize-14469.58.B-ishstabilize-14469.41.B-ishstabilize-14442.B-ishstabilize-14438.B-ishstabilize-14411.B-ishstabilize-14396.B-ishstabilize-14395.B-ishstabilize-14388.62.B-ishstabilize-14388.61.B-ishstabilize-14388.52.B-ishstabilize-14385.B-ishstabilize-14345.B-ishstabilize-14336.B-ishstabilize-14333.B-ishrelease-R99-14469.B-ishrelease-R98-14388.B-ishrelease-R102-14695.B-ishrelease-R101-14588.B-ishrelease-R100-14526.B-ishfirmware-cherry-14454.B-ishfirmware-brya-14505.B-ishfirmware-brya-14505.71.B-ishfactory-kukui-14374.B-ishfactory-guybrush-14600.B-ishfactory-cherry-14455.B-ishfactory-brya-14517.B-ish
In the interest of making long-term branch maintenance incur as little
technical debt on us as possible, we should not maintain any files on
the branch we are not actually using.
This has the added effect of making it extremely clear when merging CLs
from the main branch when changes have the possibility to affect us.
The follow-on CL adds a convenience script to actually pull updates from
the main branch and generate a CL for the update.
BUG=b:204206272
BRANCH=ish
TEST=make BOARD=arcada_ish && make BOARD=drallion_ish
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I17e4694c38219b5a0823e0a3e55a28d1348f4b18
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3262038
Reviewed-by: Jett Rink <jettrink@chromium.org>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Diffstat (limited to 'util/check_allowed.sh')
-rwxr-xr-x | util/check_allowed.sh | 88 |
1 files changed, 0 insertions, 88 deletions
diff --git a/util/check_allowed.sh b/util/check_allowed.sh deleted file mode 100755 index 0881409036..0000000000 --- a/util/check_allowed.sh +++ /dev/null @@ -1,88 +0,0 @@ -#!/bin/bash -# -# Copyright 2021 The Chromium OS Authors. All rights reserved. -# Use of this source code is governed by a BSD-style license that can be -# found in the LICENSE file. -# -# Taken from U-Boot and modified. -# -# Check that the .config file provided does not introduce any new ad-hoc CONFIG -# options -# -# Use util/build_allowed.sh to generate the list of current ad-hoc -# CONFIG options (those which are not in Kconfig). - -# Usage -# check_allowed.sh <path to .config> <path to allow file> <source dir> -# -# For example: -# scripts/check_allowed.sh build/volteer/.config config_allowed.txt . - -set -e -set -u - -PROG_NAME="${0##*/}" - -usage() { - echo >&2 "Check that a build does not introduce new ad-hoc CONFIGs" - echo >&2 "Usage:" - echo -e >&2 "\t${PROG_NAME} <.config file> <allow file> <source dir>" - exit 1 -} - -[ $# -ge 3 ] || usage - -config="$1" -allow="$2" -srctree="$3" - -tmp=$(mktemp -d) - -# Temporary files -new_configs="${tmp}/configs" -suspects="${tmp}/suspects" -kconfigs="${tmp}/kconfigs" -ok="${tmp}/ok" -new_adhoc="${tmp}/adhoc" - -export LC_ALL=C LC_COLLATE=C - -# Get a sorted list of CONFIG options in the .config file -sed -n 's/^\(CONFIG_[A-Za-z0-9_]*\).*/\1/p' "${config}" | sort | uniq \ - >"${new_configs}" - -# Find any not mentioned in the allowed file -comm -23 "${new_configs}" "${allow}" > "${suspects}" - -# Find all the Kconfig options so far defined -find "${srctree}" -type f -name "Kconfig*" -exec cat {} \; | sed -n -e \ - 's/^\s*\(config\|menuconfig\) *\([A-Za-z0-9_]*\)$/CONFIG_\2/p' \ - | sort | uniq > "${kconfigs}" - -# Most Kconfigs follow the pattern of CONFIG_PLATFORM_EC_*. Strip PLATFORM_EC_ -# from the config name to match the cros-ec namespace. -sed -e 's/^CONFIG_PLATFORM_EC_/CONFIG_/p' "${kconfigs}" | sort | uniq > "${ok}" - -# Complain about any new ad-hoc CONFIGs -comm -23 "${suspects}" "${ok}" >"${new_adhoc}" -if [ -s "${new_adhoc}" ]; then - echo >&2 "Error: The EC is in the process of migrating to Zephyr." - echo -e >&2 "\tZephyr uses Kconfig for configuration rather than" - echo -e >&2 "\tad-hoc #defines." - echo -e >&2 "\tAny new EC CONFIG options must ALSO be added to Zephyr" - echo -e >&2 "\tso that new functionality is available in Zephyr also." - echo -e >&2 "\tThe following new ad-hoc CONFIG options were detected:" - echo >&2 - cat >&2 "${new_adhoc}" - echo >&2 - echo >&2 "Please add these via Kconfig instead. Find a suitable Kconfig" - echo >&2 "file in zephyr/ and add a 'config' or 'menuconfig' option." - echo >&2 "Also see details in http://issuetracker.google.com/181253613" - echo >&2 - echo >&2 "To temporarily disable this, use: ALLOW_CONFIG=1 make ..." -else - # Check if we can remove some things from the allowed file - ./util/build_allowed.sh -fi - -rm -rf "${tmp}" |