summaryrefslogtreecommitdiff
path: root/configs/bf561-ezkit_defconfig
diff options
context:
space:
mode:
authorStefan Roese <sr@denx.de>2015-05-29 11:47:32 +0200
committerTom Rini <trini@konsulko.com>2015-06-08 10:45:04 -0400
commit20c20826efabf9ed64f5555bc8739bdbb89c1edd (patch)
treee07a48b49d8ba857a44e5a5be5df98178c068e81 /configs/bf561-ezkit_defconfig
parent4d80051b63ff54f6b6f90fceb92cf87ab3401ecb (diff)
downloadu-boot-imx-20c20826efabf9ed64f5555bc8739bdbb89c1edd.zip
u-boot-imx-20c20826efabf9ed64f5555bc8739bdbb89c1edd.tar.gz
u-boot-imx-20c20826efabf9ed64f5555bc8739bdbb89c1edd.tar.bz2
Kconfig: Enable usage of escape char '\' in string values
I might have missed something, but I failed to use the escape char '\' in strings. To pass a printf format string like "foo %d bar\n" via Kconfig to the code. Right now its not possible to use the escape character '\' in Kconfig string values correctly to e.g. set this string value "test output\n". The '\n' will be converted to 'n'. The current implementation removes some of the '\' chars from the input string in conf_set_sym_val(). Examples: '\' -> '' '\\' -> '\' '\\\' -> '\' '\\\\' -> '\\' ... And then doubles the backslash chars in the output string in sym_escape_string_value(). Example: '\' -> '' -> '' '\\' -> '\' -> '\\' '\\\' -> '\' -> '\\' '\\\\' -> '\\' -> '\\\\' ... As you see in these examples, its impossible to generate a single '\' charater in the output string as its needed for something like '\n'. This patch now changes this behavior to not drop some backslashes in conf_set_sym_val() and to not add new backslashes in the resulting output string. Removing the function sym_escape_string_value() completely as its not needed anymore. Signed-off-by: Stefan Roese <sr@denx.de> Cc: Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: Simon Glass <sjg@chromium.org> Cc: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'configs/bf561-ezkit_defconfig')
0 files changed, 0 insertions, 0 deletions