mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] uncompress: make use of error_fn in uncompress_buf_to_buf
Date: Tue, 10 Oct 2023 16:36:48 +0200	[thread overview]
Message-ID: <20231010143648.GG3114228@pengutronix.de> (raw)
In-Reply-To: <20231009115310.2398292-1-a.fatoum@pengutronix.de>

On Mon, Oct 09, 2023 at 01:53:10PM +0200, Ahmad Fatoum wrote:
> uncompress_buf_to_buf already accepts an error_fn, but didn't make use
> of it and instead relied on the default uncompress_err_stdout.
> 
> Fix this. The user-visible effect of this is that failure to decompress
> FIT image contents is now printed with pr_err instead of the default
> printf. No other upstream users of uncompress_buf_to_buf currently exist.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
>  lib/uncompress.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied, thanks

Sascha

> 
> diff --git a/lib/uncompress.c b/lib/uncompress.c
> index 0608e9f9d30f..71ac882b87fe 100644
> --- a/lib/uncompress.c
> +++ b/lib/uncompress.c
> @@ -199,7 +199,7 @@ ssize_t uncompress_buf_to_buf(const void *input, size_t input_len,
>  		goto free_temp;
>  	}
>  
> -	ret = uncompress_buf_to_fd(input, input_len, outfd, uncompress_err_stdout);
> +	ret = uncompress_buf_to_fd(input, input_len, outfd, error_fn);
>  	if (ret)
>  		goto close_outfd;
>  
> -- 
> 2.39.2
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2023-10-10 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 11:53 Ahmad Fatoum
2023-10-10 14:36 ` 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=20231010143648.GG3114228@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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