> Second, the probe and remove functions do not communicate whether an add
> or remove was successful. Combine this with the lack of port
> information in the adapter sysfs directory, and the userspace tool has
> no way of verifying a dynamic add/remove.
One way to communicate a return code is by making the sysfs interface
file read/write, and having the read callback give a return code. For
an example of this, you can look at drivers/pci/rpadlpar_sysfs.c and
rpadlpar_core.c.
It would still be nice to have some way from the adapter sysfs directory
to list/examine logical ports. Symlinks would work, but it would be
even nicer to have a new kobject per port with attribute files for
logical id, state, etc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
