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] video: vpl: don't print only skipped vpl endpoints
Date: Wed, 4 Jan 2023 11:52:38 +0100	[thread overview]
Message-ID: <20230104105238.GS11668@pengutronix.de> (raw)
In-Reply-To: <20221222115759.855209-1-a.fatoum@pengutronix.de>

On Thu, Dec 22, 2022 at 12:57:59PM +0100, Ahmad Fatoum wrote:
> The remote_vpl->ioctl is within a loop and every time an iteration is
> skipped, a debug line is printed, but no debug line is printed when the
> loop actually finds a remote_vpl to call its ioctl callback.
> 
> Make this debugging code more useful by adding a debug print in the
> latter case.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
>  drivers/video/vpl.c | 1 +
>  1 file changed, 1 insertion(+)

Applied, thanks

Sascha

> 
> diff --git a/drivers/video/vpl.c b/drivers/video/vpl.c
> index f94bd4a3e2f3..6d6786168114 100644
> --- a/drivers/video/vpl.c
> +++ b/drivers/video/vpl.c
> @@ -93,6 +93,7 @@ int vpl_ioctl(struct vpl *vpl, unsigned int port,
>  			continue;
>  		}
>  
> +		pr_debug("%s: looked up %s: %pS\n", __func__, remote->full_name, remote_vpl->ioctl);
>  		ret = remote_vpl->ioctl(remote_vpl, remote_port_id, cmd, ptr);
>  		if (ret)
>  			return ret;
> -- 
> 2.30.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-01-04 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 11:57 Ahmad Fatoum
2023-01-04 10:52 ` 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=20230104105238.GS11668@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