/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/fping/ |
H A D | fping_5.1.bb | 4 responding. fping differs from ping in that you can specify any number of \
|
/openbmc/linux/drivers/usb/class/ |
H A D | cdc-wdm.c | 250 int responding; in wdm_int_callback() local 309 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_int_callback() 310 if (!desc->resp_count++ && !responding in wdm_int_callback() 980 int responding; in wdm_rxwork() local 986 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork() 988 if (!responding) in wdm_rxwork()
|
/openbmc/linux/Documentation/devicetree/bindings/bus/ |
H A D | baikal,bt1-apb.yaml | 18 device not responding on timeout an IRQ is raised with an erroneous address
|
H A D | baikal,bt1-axi.yaml | 20 some peripherals). In case of any protocol error, device not responding
|
/openbmc/openbmc-test-automation/extended/ |
H A D | factory_reset.robot | 54 # Check whether serial console IP is reachable and responding
|
/openbmc/linux/Documentation/admin-guide/nfs/ |
H A D | pnfs-block-server.rst | 23 If the nfsd server needs to fence a non-responding client it calls
|
/openbmc/linux/Documentation/networking/device_drivers/atm/ |
H A D | cxacru.rst | 10 module loaded, the device will sometimes stop responding after unloading the
|
/openbmc/linux/drivers/scsi/mpt3sas/ |
H A D | mpt3sas_base.h | 572 u8 responding; member 635 u8 responding; member 724 u8 responding; member 818 u8 responding; member
|
H A D | mpt3sas_scsih.c | 9737 sas_device->responding = 1; in _scsih_mark_responding_sas_device() 9907 pcie_device->responding = 1; in _scsih_mark_responding_pcie_device() 10029 raid_device->responding = 1; in _scsih_mark_responding_raid_device() 10159 sas_expander->responding = 1; in _scsih_mark_responding_expander() 10266 if (!sas_device->responding) in _scsih_remove_unresponding_devices() 10269 sas_device->responding = 0; in _scsih_remove_unresponding_devices() 10297 if (!pcie_device->responding) in _scsih_remove_unresponding_devices() 10300 pcie_device->responding = 0; in _scsih_remove_unresponding_devices() 10315 if (!raid_device->responding) in _scsih_remove_unresponding_devices() 10319 raid_device->responding = 0; in _scsih_remove_unresponding_devices() [all …]
|
/openbmc/linux/drivers/bus/ |
H A D | Kconfig | 49 not responding on timeout an IRQ is raised with an erroneous address 66 any bus protocol errors and device not responding situations by
|
/openbmc/bmcweb/ |
H A D | OWNERS | 45 # - Be capable of responding to CVE queries forwarded from the
|
H A D | COMMON_ERRORS.md | 210 ## 11. Not responding to 404
|
/openbmc/docs/security/ |
H A D | obmc-security-response-team-guidelines.md | 4 response team, project owners, and community members who are responding to 185 roles, technical skills, and expertise responding to security incidents.
|
H A D | network-security-considerations.md | 54 Per [CVE 1999-0524][], responding to certain ICMP packets can give an attacker more
|
/openbmc/linux/Documentation/i2c/ |
H A D | fault-codes.rst | 91 an I2C device was temporarily not responding, usually it
|
/openbmc/linux/Documentation/process/ |
H A D | 2.Process.rst | 426 - When responding to linux-kernel email (or that on other lists) preserve 429 sure that the person you are responding to is in the Cc: list. This 439 the quoted text you are responding to.) For more details, see
|
/openbmc/linux/Documentation/watchdog/ |
H A D | watchdog-api.rst | 48 still responding before doing the write call to ping the watchdog.
|
/openbmc/linux/Documentation/filesystems/ |
H A D | configfs.rst | 321 responsible for responding to this. If the subsystem has references to 424 responsible for responding to the change.
|
H A D | fuse.rst | 178 not responding. Reasons for this may be:
|
/openbmc/linux/Documentation/PCI/ |
H A D | pci.rst | 372 - Disable device from responding to MMIO/IO Port addresses 437 Disable Device from responding to MMIO/IO Port addresses
|
/openbmc/qemu/docs/ |
H A D | COLO-FT.txt | 90 the heartbeat stops responding, the secondary node will trigger a failover
|
/openbmc/linux/Documentation/hwmon/ |
H A D | abituguru-datasheet.rst | 12 the program inside the uC that is responding to calls.
|
/openbmc/linux/Documentation/driver-api/surface_aggregator/ |
H A D | ssh.rst | 144 the frame by responding with a message containing an |ACK|-type frame with
|
/openbmc/qemu/docs/system/devices/ |
H A D | usb.rst | 388 the device not responding any more until you power-cycle (aka un-plug
|
/openbmc/linux/Documentation/scsi/ |
H A D | aic79xx.rst | 496 to stop responding.
|