From: Clemens Ladisch <clemens@ladisch.de>
To: Nicholas Krause <xerofoify@gmail.com>, stefanr@s5r6.in-berlin.de
Cc: linux-media@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, mchehab@osg.samsung.com
Subject: Re: [PATCH] media; firewire: Remove no longer needed fix me comment in firedtv-ci.c for the function,fdtv_ca_ioctl
Date: Sat, 10 Jan 2015 00:02:29 +0100 [thread overview]
Message-ID: <54B05E05.3090409@ladisch.de> (raw)
In-Reply-To: <1420838221-3957-1-git-send-email-xerofoify@gmail.com>
Nicholas Krause wrote:
> Removes the no longer fix me comment for if we need to set the tuner status with
> the line, avc_tuner_status(fdtv, &stat). This line is needed in order to set the
> tuner status after we have through the switch statement checking what fdtv function
> we need to call to use to try and setup the hardware successfully.
You have attempted to describe what fdtv_ca_ioctl() does, but your description
lacks any understanding of what avc_tuner_status() does, or how it might affect
the device, or whether it is necessary.
Please stop spamming us with useless patches.
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> drivers/media/firewire/firedtv-ci.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/media/firewire/firedtv-ci.c b/drivers/media/firewire/firedtv-ci.c
> index e63f582..9c038ba 100644
> --- a/drivers/media/firewire/firedtv-ci.c
> +++ b/drivers/media/firewire/firedtv-ci.c
> @@ -201,7 +201,6 @@ static int fdtv_ca_ioctl(struct file *file, unsigned int cmd, void *arg)
> err = -EOPNOTSUPP;
> }
>
> - /* FIXME Is this necessary? */
> avc_tuner_status(fdtv, &stat);
>
> return err;
parent reply other threads:[~2015-01-09 23:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1420838221-3957-1-git-send-email-xerofoify@gmail.com>]
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=54B05E05.3090409@ladisch.de \
--to=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mchehab@osg.samsung.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=xerofoify@gmail.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.