All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luiz Fernando N. Capitulino" <lcapitulino@prefeitura.sp.gov.br>
To: Zhenmin Li <zli4@cs.uiuc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OPERA] Potential bugs detected by static analysis tool in 2.6.4
Date: Thu, 6 May 2004 21:14:07 -0300	[thread overview]
Message-ID: <20040507001407.GK9037@lorien.prodam> (raw)
In-Reply-To: <002701c4331c$092a3b40$76f6ae80@Turandot>


 Hi Zhenmin,

Em Wed, May 05, 2004 at 10:41:37PM -0500, Zhenmin Li escreveu:

| 9. /drivers/pci/hotplug/shpchp_ctrl.c, Line 1575:
| err("%s: Failed to disable slot, error code(%d)\n", __FUNCTION__, rc);
| 
| Maybe change to:
| err("%s: Failed to disable slot, error code(%d)\n", __FUNCTION__, retval);

 This seems right to me.

| 
| 10. /sound/oss/swarm_cs4297a.c, Line 2019:
| s->dma_adc.blocks = s->dma_dac.wakeup = 0;
| 
| Maybe change to:
| s->dma_adc.blocks = s->dma_adc.wakeup = 0;

 This don't. At a first look seems that 'dma_adc' and 'dma_dac' is the some
thing typed wrong, but don't, they are not the some thing.

-- 
Luiz Fernando N. Capitulino
<http://www.telecentros.sp.gov.br>

  parent reply	other threads:[~2004-05-07  0:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06  3:41 [OPERA] Potential bugs detected by static analysis tool in 2.6.4 Zhenmin Li
2004-05-06  9:43 ` Geert Uytterhoeven
2004-05-06 16:29   ` Brad Boyer
2004-05-06 16:44   ` Zhenmin Li
2004-05-06 20:22     ` Brad Boyer
2004-05-07  0:14 ` Luiz Fernando N. Capitulino [this message]
2004-05-07 22:22   ` [OPERA] Another potential error detected by static analysis tool (2.6.4) Zhenmin Li
2004-05-07 23:07     ` Andreas Dilger
     [not found] <002701c4331c$092a3b40$76f6ae80@Turandot.suse.lists.linux.kernel>
2004-05-06  7:14 ` [OPERA] Potential bugs detected by static analysis tool in 2.6.4 Andi Kleen

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=20040507001407.GK9037@lorien.prodam \
    --to=lcapitulino@prefeitura.sp.gov.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zli4@cs.uiuc.edu \
    /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.