From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: nick <xerofoify@gmail.com>
Cc: mchehab@osg.samsung.com, linux-media@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media:firewire:Remove unneeded function definition,avc_tuner_host2ca in firedtv-avc.c
Date: Mon, 9 Feb 2015 07:43:02 +0100 [thread overview]
Message-ID: <20150209074302.79876412@kant> (raw)
In-Reply-To: <54D80CCC.5030700@gmail.com>
On Feb 08 nick wrote:
> On 2015-02-08 06:55 PM, Stefan Richter wrote:
> > I still am missing research on the question whether or not the Common
> > Interface serving part of the driver needs to send Host2CA commands. If
> > yes, we implement it and use the function. If not, we remove the
> > function. As long as we are not sure, I prefer to leave the #if-0'd code
> > where it is. It documents how the command is formed, and we don't have
> > any other documentation (except perhaps the git history).
[...]
> Stefan,
> I looked in the history with git log -p 154907957f939 and all I got
> for this function was
> Wed Feb 11 21:21:04 CET 2009
> firedtv: avc: header file cleanup
>
> Remove unused constants and declarations.
> Move privately used constants into .c files.
The function was added a few commits before this one, by "firesat: update
isochronous interface, add CI support".
> Clearly this states to remove unused declarations and avc_tuner_host2ca is unused.
> Can you explain to me then why it's still needed to be around if there no callers
> of it?
See above; in this instance
#if 0
dead code
#endif
stands in for
/*
* pseudo code
*/
--
Stefan Richter
-=====-===== --=- -=--=
http://arcgraph.de/sr/
prev parent reply other threads:[~2015-02-09 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1423423437-31949-1-git-send-email-xerofoify@gmail.com>
2015-02-08 23:55 ` [PATCH] media:firewire:Remove unneeded function definition,avc_tuner_host2ca in firedtv-avc.c Stefan Richter
[not found] ` <54D80CCC.5030700@gmail.com>
2015-02-09 6:43 ` Stefan Richter [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=20150209074302.79876412@kant \
--to=stefanr@s5r6.in-berlin.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox