> Alan, what's the approach you'd feel more comfortable with: > - One ioctl that passes a pointer to a known structure in ifr.ifr_data as > its argument. > - Several ioctl's, one for each parameter, that pass only the specific > parameter new value as the argument. > > The former is good because it relies on a _single_ ioctl. However, every > time you change the ioctl structure you may lose backward compatibility. One ioctl with a set of subcommands seems to be quite common - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- [RFC-2] Configuring Synchronous Interfaces in Linux Ivan Passos
- Re: [RFC-2] Configuring Synchronous Interfaces in Li... Francois Romieu
- Re: [RFC-2] Configuring Synchronous Interfaces in Li... Alan Cox
- Re: [RFC-2] Configuring Synchronous Interfaces i... Greg Parrott
- Re: [RFC-2] Configuring Synchronous Interfaces i... Ivan Passos
- Re: [RFC-2] Configuring Synchronous Interfac... Peter Samuelson
- Re: [RFC-2] Configuring Synchronous Interfac... Alan Cox
- Re: [RFC-2] Configuring Synchronous Interfaces in Li... Matthew G. Marsh
- Re: [RFC-2] Configuring Synchronous Interfaces in Li... Paul Fulghum
- Re: [RFC-2] Configuring Synchronous Interfaces in Li... Ivan Passos
- Re: [RFC-2] Configuring Synchronous Interfaces in Li... Stuart Lynne
- Re: [RFC-2] Configuring Synchronous Interfaces i... Alan Cox
- Re: [RFC-2] Configuring Synchronous Interfac... Dan Hollis
- Re: [RFC-2] Configuring Synchronous Inte... Stuart Lynne
- Re: [RFC-2] Configuring Synchronous Interfac... Krzysztof Halasa