summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJakub Czapiga <czapiga@google.com>2023-03-21 15:53:11 +0100
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>2023-03-22 10:08:14 +0000
commit75ae0c48d943632741171fcda3d0a1860ab342a2 (patch)
treef4ff15cce7c905d15ed8c352c61a838d34509bb2
parent4ba3799473fc967e9edadec92c701d9d68a5c6f8 (diff)
downloadchrome-ec-75ae0c48d943632741171fcda3d0a1860ab342a2.tar.gz
util/flash_ec: Fix incorrect bitbang_rate definition
Excessive space in the definition of bitbang_rate caused this option's second line of its help string to be used as short opt. This made help output incorrect and potentially could introduce incorrect flags parsing behavior. BUG=None TEST=./util/flash_ec --help # displays correctly now BRANCH=None Change-Id: I4c9645339d84fdaec19c0cc33358883c8fddf4be Signed-off-by: Jakub Czapiga <czapiga@google.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/4355420 Reviewed-by: Peter Marheine <pmarheine@chromium.org>
-rwxr-xr-xutil/flash_ec2
1 files changed, 1 insertions, 1 deletions
diff --git a/util/flash_ec b/util/flash_ec
index 5a81cc4759..93406c0793 100755
--- a/util/flash_ec
+++ b/util/flash_ec
@@ -147,7 +147,7 @@ BITBANG_RATE="57600" # Could be overwritten by a command line option.
# Flags
DEFINE_integer bitbang_rate "${BITBANG_RATE}" \
- "UART baud rate to use when bit bang programming, " \
+ "UART baud rate to use when bit bang programming, "\
"standard UART rates from 9600 to 57600 are supported."
DEFINE_string board "" \
"The board to run debugger on."