RFC add fc transport events

The following patches begin to address the problem of allowing a userspace program to online or offline a scsi device. The major change is the layout of the transport class so that devices are presented under an adapter with the fc_transport class node the root for adapters. There's still no adapter level attributes so the host's class_device is really just being used as way to nicely structure things, and the class_device in the scsi_device has been converted to a kobject.

Here is a partial tree:

elm3a38:/sys/class/fc_transport # tree
.

|-- host4
|   |-- 4:0:0:0
|   |   |-- node_name
|   |   |-- port_id
|   |   `-- port_name
|   |-- 4:0:1:0
|   |   |-- node_name
|   |   |-- port_id
|   |   `-- port_name
|   `-- device -> ../../../devices/pci0000:02/0000:02:03.0/host4
`-- host5
    |-- 5:0:0:0
    |   |-- node_name
    |   |-- port_id
    |   `-- port_name
    |-- 5:0:1:0

.
.
.

01-add-host-transport-classdev.patch - adds the transport class_device to the scsi_host structure.

02-sdev-transport-kobj.patch - converts the transport class_device in the scsi_device to a kobject.

03-convert-fc-class.patch - converts the fc class from a class_device scsi_device to a kobject and adds a basic link_up/down event fucntion.

(I did not convert the spi class yet, becuase I wasn't sure how people would feel about such a change)

Mike Christie