From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>
Cc: Arnaud Patard <arnaud.patard@rtp-net.org>,
devel@driverdev.osuosl.org, Aaro Koskinen <aaro.koskinen@iki.fi>,
linux-kernel@vger.kernel.org,
Vitor Braga <vitorpybraga@gmail.com>,
Thomas Gummerer <t.gummerer@gmail.com>
Subject: Re: [PATCH] staging: xgifb: vb_init: Removed variables that is never used
Date: Sat, 31 Jan 2015 20:19:48 -0800 [thread overview]
Message-ID: <20150201041948.GA25151@kroah.com> (raw)
In-Reply-To: <1422717648-7274-1-git-send-email-rickard_strandqvist@spectrumdigital.se>
On Sat, Jan 31, 2015 at 04:20:48PM +0100, Rickard Strandqvist wrote:
> Variable was assigned a value that was never used.
> I have also removed all the code that thereby serves no purpose.
>
> This was found using a static code analysis program called cppcheck
>
> Signed-off-by: Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>
> ---
> drivers/staging/xgifb/vb_init.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/staging/xgifb/vb_init.c b/drivers/staging/xgifb/vb_init.c
> index 2b233af..6384077 100644
> --- a/drivers/staging/xgifb/vb_init.c
> +++ b/drivers/staging/xgifb/vb_init.c
> @@ -1187,7 +1187,7 @@ unsigned char XGIInitNew(struct pci_dev *pdev)
> struct xgi_hw_device_info *HwDeviceExtension = &xgifb_info->hw_info;
> struct vb_device_info VBINF;
> struct vb_device_info *pVBInfo = &VBINF;
> - unsigned char i, temp = 0, temp1;
> + unsigned char i, temp = 0;
>
> pVBInfo->FBAddr = HwDeviceExtension->pjVideoMemoryAddress;
>
> @@ -1286,8 +1286,6 @@ unsigned char XGIInitNew(struct pci_dev *pdev)
> /* disable VideoCapture */
> xgifb_reg_and_or(pVBInfo->Part0Port, 0x3F, 0xEF, 0x00);
> xgifb_reg_set(pVBInfo->Part1Port, 0x00, 0x00);
> - /* chk if BCLK>=100MHz */
> - temp1 = xgifb_reg_get(pVBInfo->P3d4, 0x7B);
With hardware, you can't just remove all 'read' calls and expect things
to work because a static code checker things something is not right.
I'm going to drop _all_ of the patches you sent me in the past few days
as I really think they all are wrong. Please be more careful and work
on fixing real problems, not just ones that random tools think might be
wrong. Weeding out false-positives should not be my job, that's not
scalable at all.
sorry,
greg k-h
prev parent reply other threads:[~2015-02-01 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 15:20 [PATCH] staging: xgifb: vb_init: Removed variables that is never used Rickard Strandqvist
2015-02-01 4:19 ` Greg Kroah-Hartman [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=20150201041948.GA25151@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aaro.koskinen@iki.fi \
--cc=arnaud.patard@rtp-net.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rickard_strandqvist@spectrumdigital.se \
--cc=t.gummerer@gmail.com \
--cc=vitorpybraga@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.