mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Enrico Jorns <ejo@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v3 0/6] Fixes for nv command handling
Date: Fri, 3 Nov 2017 08:51:35 +0100	[thread overview]
Message-ID: <20171103075135.bmzhc5nilae4kit6@pengutronix.de> (raw)
In-Reply-To: <20171101072710.31518-1-ejo@pengutronix.de>

On Wed, Nov 01, 2017 at 08:27:04AM +0100, Enrico Jorns wrote:
> This series adds a couple of fixes and enhancement in option parsing and error
> handling for the 'nv' command.
> 
> CHANGES:
> 
> * Add missing curly braces in 1/5
> * properly introduce and use NV abbreviation
> * re-align help text

Applied, thanks

Sascha

> 
> Enrico Jorns (6):
>   commands: nv: fail with verbose message if invoked without args
>   commands: nv: call nvvar_print() only if no argument is given
>   commands: nv: assure error code will be returned when an error
>     occurred
>   common: globvar: let nvvar_remove() report non-existing variable
>   commands: nv: adjust command help
>   command: nv: rewrap help text lines
> 
>  commands/nv.c      | 45 +++++++++++++++++++++++++++++----------------
>  common/globalvar.c |  4 +++-
>  2 files changed, 32 insertions(+), 17 deletions(-)
> 
> -- 
> 2.11.0
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2017-11-03  7:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01  7:27 Enrico Jorns
2017-11-01  7:27 ` [PATCH 1/6] commands: nv: fail with verbose message if invoked without args Enrico Jorns
2017-11-01  7:27 ` [PATCH 2/6] commands: nv: call nvvar_print() only if no argument is given Enrico Jorns
2017-11-01  7:27 ` [PATCH 3/6] commands: nv: assure error code will be returned when an error occurred Enrico Jorns
2017-11-01  7:27 ` [PATCH 4/6] common: globvar: let nvvar_remove() report non-existing variable Enrico Jorns
2017-11-01  7:27 ` [PATCH 5/6] commands: nv: adjust command help Enrico Jorns
2017-11-01  7:27 ` [PATCH 6/6] command: nv: rewrap help text lines Enrico Jorns
2017-11-03  7:51 ` Sascha Hauer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171103075135.bmzhc5nilae4kit6@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=ejo@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox