Why EIO used instead of EBUSY in device drivers???

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Hi,

    I was looking at the initialization code for TUN/TAP and mwave devices, 
both those places they return a  -EIO error code when they fail to 
initialize a device. the misc_register which they call the initialize the 
device return a EBUSY. Should'nt the device driver also return EBUSY as an 
error during registering a device is EBUSY not EIO!!!!!
   Or is it the case that the misc_register should check if it was an EIO 
and not EBUSY>????????


thanks
gaurav

_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux