question about drivers/atm/firestream.c

2 messages, 2 authors, 2009-08-17 · open the first message on its own page

question about drivers/atm/firestream.c

From: Julia Lawall <hidden>
Date: 2009-08-15 17:08:08

In the file drivers/atm/firestream.c in the function fs_open, there is the 
following code:

       if (vci != ATM_VPI_UNSPEC && vpi != ATM_VCI_UNSPEC)
                set_bit(ATM_VF_ADDR, &atm_vcc->flags);

Should ATM_VPI_UNSPEC and ATM_VCI_UNSPEC be exchanged?  They have the same 
value, but the code looks a bit odd this way nonetheless.

thanks,
julia

Re: question about drivers/atm/firestream.c

From: Chas Williams (CONTRACTOR) <hidden>
Date: 2009-08-17 14:34:39

In message [off-list ref],Julia Lawall writes:
In the file drivers/atm/firestream.c in the function fs_open, there is the 
following code:

      if (vci != ATM_VPI_UNSPEC && vpi != ATM_VCI_UNSPEC)
               set_bit(ATM_VF_ADDR, &atm_vcc->flags);

Should ATM_VPI_UNSPEC and ATM_VCI_UNSPEC be exchanged?  They have the same 
value, but the code looks a bit odd this way nonetheless.
yes this is backwards.  this whole UNSPEC business should really go away.
drivers should never need to worry about getting an unspecified vpi or
vci.  this should be chosen by the next layer up in the stack.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help