mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Aleksander Morgado <aleksander@aleksander.es>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] lib,ratp: avoid too verbose info messages
Date: Wed, 20 Sep 2017 08:53:23 +0200	[thread overview]
Message-ID: <20170920065323.nyk4p37ttam5du6q@pengutronix.de> (raw)
In-Reply-To: <20170919213641.28512-1-aleksander@aleksander.es>

On Tue, Sep 19, 2017 at 02:36:41PM -0700, Aleksander Morgado wrote:
> When using a cli-based RATP that opens and closes the RATP channel for
> each command sent/received, it gets annoying to get the "Closed"
> message printed all the time in console after each RATP channel close
> operation. Just demote it to debug level.
> 
> E.g.:
>     barebox@barebox sandbox:/ ratp: Closed
>     ratp: Closed
>     ratp: Closed
>     ratp: Closed
>     ...
> 
> Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
> ---
>  lib/ratp.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied, thanks

Sascha

> 
> diff --git a/lib/ratp.c b/lib/ratp.c
> index e7fbf640a..4c5c748b4 100644
> --- a/lib/ratp.c
> +++ b/lib/ratp.c
> @@ -1717,7 +1717,7 @@ void ratp_close(struct ratp *ratp)
>  	free(ri);
>  	ratp->internal = NULL;
>  
> -	pr_info("Closed\n");
> +	pr_debug("Closed\n");
>  }
>  
>  /**
> -- 
> 2.14.1
> 
> 

-- 
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

      reply	other threads:[~2017-09-20  6:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 21:36 Aleksander Morgado
2017-09-20  6:53 ` 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=20170920065323.nyk4p37ttam5du6q@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=aleksander@aleksander.es \
    --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