From: Benoit Fouet <benoit.fouet@purplelabs.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] sound/pci/cs46xx/cs46xx_lib.c: remove unused variable
Date: Fri, 08 Aug 2008 12:05:53 +0000 [thread overview]
Message-ID: <489C36A1.2030801@purplelabs.com> (raw)
In-Reply-To: <1218195562.4609.7.camel@niro-laptop>
Hi,
Michael Borisov wrote:
> This patch fixes the following compile warning:
> sound/pci/cs46xx/cs46xx_lib.c: In function ‘snd_cs46xx_resume’:
> sound/pci/cs46xx/cs46xx_lib.c:3614: warning: unused variable ‘i’
>
> cs46xx_lib.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> Signed-off-by: Michael Borisov <niro@tut.by>
> ---
> diff --git a/sound/pci/cs46xx/cs46xx_lib.c
> b/sound/pci/cs46xx/cs46xx_lib.c
> index e214e56..07bb7e0 100644
> --- a/sound/pci/cs46xx/cs46xx_lib.c
> +++ b/sound/pci/cs46xx/cs46xx_lib.c
> @@ -3611,7 +3611,7 @@ int snd_cs46xx_resume(struct pci_dev *pci)
> {
> struct snd_card *card = pci_get_drvdata(pci);
> struct snd_cs46xx *chip = card->private_data;
> - int i, amp_saved;
> + int amp_saved;
>
> pci_set_power_state(pci, PCI_D0);
> pci_restore_state(pci);
> @@ -3633,6 +3633,7 @@ int snd_cs46xx_resume(struct pci_dev *pci)
> #ifdef CONFIG_SND_CS46XX_NEW_DSP
> cs46xx_dsp_resume(chip);
> /* restore some registers */
> + int i;
>
why not ifdef'ing the declaration earlier.
doing it the way you are way, you mix declaration and code.
(I don't know what the kernel policy is for this matter)
--
Benoit Fouet
Purple Labs S.A.
www.purplelabs.com
next prev parent reply other threads:[~2008-08-08 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 11:39 [PATCH] sound/pci/cs46xx/cs46xx_lib.c: remove unused variable Michael Borisov
2008-08-08 11:39 ` [PATCH] sound/pci/cs46xx/cs46xx_lib.c: remove unused variable warning Michael Borisov
2008-08-08 12:05 ` Benoit Fouet [this message]
2008-08-08 15:42 ` [PATCH] sound/pci/cs46xx/cs46xx_lib.c: remove unused variable Rene Herman
2008-08-08 15:42 ` [PATCH] sound/pci/cs46xx/cs46xx_lib.c: remove unused variable warning Rene Herman
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=489C36A1.2030801@purplelabs.com \
--to=benoit.fouet@purplelabs.com \
--cc=kernel-janitors@vger.kernel.org \
/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.