All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <snjw23@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	Andy Walls <awalls@md.metrocast.net>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Steven Toth <stoth@kernellabs.com>,
	Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH 1/2] v4l2: standardize log start/end message.
Date: Fri, 27 Jan 2012 21:50:50 +0100	[thread overview]
Message-ID: <4F230E2A.4080203@gmail.com> (raw)
In-Reply-To: <1844c31eb7b4515904824a6b26994f7bdd7eace8.1327686924.git.hans.verkuil@cisco.com>

Hello Hans,

On 01/27/2012 06:59 PM, Hans Verkuil wrote:
> diff --git a/drivers/media/video/v4l2-ioctl.c b/drivers/media/video/v4l2-ioctl.c
> index d0d7281..2348669 100644
> --- a/drivers/media/video/v4l2-ioctl.c
> +++ b/drivers/media/video/v4l2-ioctl.c
> @@ -1911,7 +1911,15 @@ static long __video_do_ioctl(struct file *file,
>   	{
>   		if (!ops->vidioc_log_status)
>   			break;
> +		if (vfd->v4l2_dev)
> +			printk(KERN_INFO
> +				"%s: =================  START STATUS  =================\n",
> +				vfd->v4l2_dev->name);
>   		ret = ops->vidioc_log_status(file, fh);
> +		if (vfd->v4l2_dev)
> +			printk(KERN_INFO
> +				"%s: ==================  END STATUS  ==================\n",
> +				vfd->v4l2_dev->name);

Nice cleanup, but wouldn't it be more appropriate to use pr_info() here
instead ? AFAIK this is preferred logging style now.

--

Thanks,
Sylwester

      parent reply	other threads:[~2012-01-27 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 17:59 [PATCH 0/2] v4l2: standardize log start/end messages Hans Verkuil
2012-01-27 17:59 ` [PATCH 1/2] v4l2: standardize log start/end message Hans Verkuil
2012-01-27 17:59   ` [PATCH 2/2] v4l2-subdev: add start/end messages for log_status Hans Verkuil
2012-01-27 20:50   ` Sylwester Nawrocki [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=4F230E2A.4080203@gmail.com \
    --to=snjw23@gmail.com \
    --cc=awalls@md.metrocast.net \
    --cc=hans.verkuil@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=stoth@kernellabs.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.