All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: mchehab@redhat.com, linux-media@vger.kernel.org
Subject: Re: [PATCH] tuner-core: return tuner name with ioctl VIDIOC_G_TUNER
Date: Wed, 23 Jan 2013 08:35:29 +0100	[thread overview]
Message-ID: <201301230835.29623.hverkuil@xs4all.nl> (raw)
In-Reply-To: <1358883981-2645-1-git-send-email-fschaefer.oss@googlemail.com>

On Tue January 22 2013 20:46:21 Frank Schäfer wrote:
> tuner_g_tuner() is supposed to fill struct v4l2_tuner passed by ioctl
> VIDIOC_G_TUNER, but misses setting the name field.
> 
> Signed-off-by: Frank Schäfer <fschaefer.oss@googlemail.com>
> Cc: stable@kernel.org
> ---
>  drivers/media/v4l2-core/tuner-core.c |    1 +
>  1 Datei geändert, 1 Zeile hinzugefügt(+)
> 
> diff --git a/drivers/media/v4l2-core/tuner-core.c b/drivers/media/v4l2-core/tuner-core.c
> index b5a819a..95a47cf 100644
> --- a/drivers/media/v4l2-core/tuner-core.c
> +++ b/drivers/media/v4l2-core/tuner-core.c
> @@ -1187,6 +1187,7 @@ static int tuner_g_tuner(struct v4l2_subdev *sd, struct v4l2_tuner *vt)
>  
>  	if (check_mode(t, vt->type) == -EINVAL)
>  		return 0;
> +	strcpy(vt->name, t->name);
>  	if (vt->type == t->mode && analog_ops->get_afc)
>  		vt->afc = analog_ops->get_afc(&t->fe);
>  	if (analog_ops->has_signal)
> 

Nacked-by: Hans Verkuil <hans.verkuil@cisco.com>

And the reason is that the tuner field should be filled in by the bridge
driver. That's because you may have multiple tuners and it's only the
bridge driver that will know which tuner is which and what name to give
it.

Regards,

	Hans

  reply	other threads:[~2013-01-23  7:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 19:46 [PATCH] tuner-core: return tuner name with ioctl VIDIOC_G_TUNER Frank Schäfer
2013-01-23  7:35 ` Hans Verkuil [this message]
2013-01-23 15:57   ` Frank Schäfer
2013-01-23 16:13     ` Hans Verkuil
2013-01-23 17:03       ` Frank Schäfer
2013-01-23 18:33         ` Hans Verkuil
2013-01-23 22:13           ` Frank Schäfer

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=201301230835.29623.hverkuil@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=fschaefer.oss@googlemail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.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.