All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Franco <stratus@acm.org>
To: kernel-janitors@vger.kernel.org
Subject: [Kernel-janitors] Re: request_region() on sound/oss/wavfront.c.
Date: Sun, 23 May 2004 01:12:10 +0000	[thread overview]
Message-ID: <40AFFA6A.1010502@acm.org> (raw)
In-Reply-To: <20040522224343.GA1643@masina>

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

Domen Puncer wrote:

>On 23/05/04 00:43 +0200, Domen Puncer wrote:
>  
>
>>On 22/05/04 18:54 -0300, Gustavo Franco wrote:
>>
>>    
>>
>>>+++ sound/oss/wavfront.c  2004-05-22 18:28:38.000000000 -0300
>>>+       if (!request_region (io_base, 16, "wavefront")) {
>>>      
>>>
>>Few lines later there is a:
>>	dev.base = io_base;
>>So this will print ugly error messages.
>>    
>>
Sorry, but do you mean KERN_ERR ones?

>>    
>>
>>>+       if(!request_region (dev.base+2, 6, "wavefront synth")) {
>>>+               if(!request_region (dev.base+8, 8, "wavefront fx")) {
>>>      
>>>
>>IMHO, you can just get rid of latter 2 request_region's.
>>    
>>
>
>Ehm, no, damn. Comment above check_region states that device can take
>up 8 ports.
>
>So if there is another device on base+8 this wont work correctly (if that
>device registred it's region before, even the old code wont work ok).
>
>  
>
What? Can you summarize your two messages? Check that both 
request_region() cited
by you above were not added by me, i've added a return check only.


Thanks,
--
Gustavo Franco

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2004-05-23  1:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22 22:43 [Kernel-janitors] Re: request_region() on sound/oss/wavfront.c Domen Puncer
2004-05-22 23:11 ` Domen Puncer
2004-05-23  1:12 ` Gustavo Franco [this message]
2004-05-23  7:09 ` Domen Puncer

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=40AFFA6A.1010502@acm.org \
    --to=stratus@acm.org \
    --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.