Re: [U-Boot] [PATCH] Fix --noheader on fw_printenv

2018-02-08 Thread Alex Kiernan
On Thu, Feb 8, 2018 at 4:40 PM, Stefan Agner wrote: > On 08.02.2018 17:17, Alex Kiernan wrote: >> On Thu, Feb 8, 2018 at 3:37 PM, wrote: >>> On 08.02.2018 10:35, Alex Kiernan wrote: Using fw_printenv with --noheader fails: root@nrr-922:~#

Re: [U-Boot] [PATCH] Fix --noheader on fw_printenv

2018-02-08 Thread Stefan Agner
On 08.02.2018 17:17, Alex Kiernan wrote: > On Thu, Feb 8, 2018 at 3:37 PM, wrote: >> On 08.02.2018 10:35, Alex Kiernan wrote: >>> Using fw_printenv with --noheader fails: >>> >>> root@nrr-922:~# fw_printenv --noheader arch >>> ## Error: `-n' option requires exactly one

Re: [U-Boot] [PATCH] Fix --noheader on fw_printenv

2018-02-08 Thread Alex Kiernan
On Thu, Feb 8, 2018 at 3:37 PM, wrote: > On 08.02.2018 10:35, Alex Kiernan wrote: >> Using fw_printenv with --noheader fails: >> >> root@nrr-922:~# fw_printenv --noheader arch >> ## Error: `-n' option requires exactly one argument > > I think it would work with

Re: [U-Boot] [PATCH] Fix --noheader on fw_printenv

2018-02-08 Thread stefan
On 08.02.2018 10:35, Alex Kiernan wrote: > Using fw_printenv with --noheader fails: > > root@nrr-922:~# fw_printenv --noheader arch > ## Error: `-n' option requires exactly one argument I think it would work with --noheader=arch > > Whereas -n works: > > root@nrr-922:~# fw_printenv -n

[U-Boot] [PATCH] Fix --noheader on fw_printenv

2018-02-08 Thread Alex Kiernan
Using fw_printenv with --noheader fails: root@nrr-922:~# fw_printenv --noheader arch ## Error: `-n' option requires exactly one argument Whereas -n works: root@nrr-922:~# fw_printenv -n arch arm The single argument it's expecting isn't taken from getopt parsing, but instead from the