Searched hist:249468 (Results 1 - 24 of 24) sorted by relevance
| /freebsd-10.2-release/sys/dev/isci/ | ||
| H A D | isci_domain.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| H A D | isci_remote_device.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| H A D | isci_controller.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/iscsi_initiator/ | ||
| H A D | isc_cam.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/tws/ | ||
| H A D | tws_cam.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/mfi/ | ||
| H A D | mfi_cam.c | diff 251172 Fri May 31 03:31:01 MDT 2013 sbruno xpt_create_path() requires mfi_io_lock to be held, so do it. mfi(4) doesn't panic on host startup now. MFC this if svn 249468-242726 is shoveled back to stable/9 Obtained from: Yahoo! Inc. diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/hpt27xx/ | ||
| H A D | hpt27xx_osm_bsd.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/virtio/scsi/ | ||
| H A D | virtio_scsi.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/hptiop/ | ||
| H A D | hptiop.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/hptrr/ | ||
| H A D | hptrr_osm_bsd.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/twa/ | ||
| H A D | tw_osl_cam.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/cam/ctl/ | ||
| H A D | ctl_frontend_cam_sim.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/arcmsr/ | ||
| H A D | arcmsr.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/aac/ | ||
| H A D | aac_cam.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/cam/ata/ | ||
| H A D | ata_xpt.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/mly/ | ||
| H A D | mly.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/mpt/ | ||
| H A D | mpt_raid.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| H A D | mpt_cam.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/cam/scsi/ | ||
| H A D | scsi_xpt.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/firewire/ | ||
| H A D | sbp.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/ciss/ | ||
| H A D | ciss.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/mps/ | ||
| H A D | mps_sas.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/dev/isp/ | ||
| H A D | isp_freebsd.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
| /freebsd-10.2-release/sys/cam/ | ||
| H A D | cam_xpt.c | diff 249468 Sun Apr 14 09:57:42 MDT 2013 mav MFprojects/camlock r248982: Stop abusing xpt_periph in random plases that really have no periph related to CCB, for example, bus scanning. NULL value is fine in such cases and it is correctly logged in debug messages as "noperiph". If at some point we need some real XPT periphs (alike to pmpX now), quite likely they will be per-bus, and not a single global instance as xpt_periph now. |
Completed in 321 milliseconds