diff options
| author | Marco Felsch <m.felsch@pengutronix.de> | 2019-10-30 18:03:39 +0100 |
|---|---|---|
| committer | Sascha Hauer <s.hauer@pengutronix.de> | 2019-11-04 10:38:52 +0100 |
| commit | 3b81d1199347b2fd250d72bb4df39e15f975b6ed (patch) | |
| tree | d1ccbb8c3fea90931bf2c80992ed576ca1b9dcb5 /drivers/usb/storage/usb.c | |
| parent | 5c06691a321c9f0d9e143c52b143366d0428391b (diff) | |
| download | barebox-3b81d1199347b2fd250d72bb4df39e15f975b6ed.tar.gz barebox-3b81d1199347b2fd250d72bb4df39e15f975b6ed.tar.xz | |
parameter: strip leading and trailing whitespaces
My initial bug was the following: I set the
global.boot.default="boot1 boot2 " and executed the 'boot' command. If
both targets are not bootable barebox starts to execute the boot scripts
found under /env/boot. This is because of the command/boot.c
implementation and the leading whitespace. Without the whitespace only
the two desired boot targets are tried.
IMHO leading and trailing whitespaces are error-prone in many cases. If
someone wants to concatenate strings he/she should add spaces on
purpose. So I fixed the bug above globally by always stripping leading
and trailing whitespaces.
Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'drivers/usb/storage/usb.c')
0 files changed, 0 insertions, 0 deletions