Searched refs:responding (Results 1 – 21 of 21) sorted by relevance
233 int responding; in wdm_int_callback() local292 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_int_callback()293 if (!desc->resp_count++ && !responding in wdm_int_callback()743 int responding; in wdm_rxwork() local749 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()751 if (!responding) in wdm_rxwork()
21 If the nfsd server needs to fence a non-responding client it calls
519 u8 responding; member577 u8 responding; member664 u8 responding; member750 u8 responding; member
8391 sas_device->responding = 1; in _scsih_mark_responding_sas_device()8563 pcie_device->responding = 1; in _scsih_mark_responding_pcie_device()8687 raid_device->responding = 1; in _scsih_mark_responding_raid_device()8815 sas_expander->responding = 1; in _scsih_mark_responding_expander()8909 if (!sas_device->responding) in _scsih_remove_unresponding_devices()8912 sas_device->responding = 0; in _scsih_remove_unresponding_devices()8932 if (!pcie_device->responding) in _scsih_remove_unresponding_devices()8935 pcie_device->responding = 0; in _scsih_remove_unresponding_devices()8951 if (!raid_device->responding) in _scsih_remove_unresponding_devices()8955 raid_device->responding = 0; in _scsih_remove_unresponding_devices()[all …]
4 module loaded, the device will sometimes stop responding after unloading the
351 tcp_keepalive_probes it is time to kill not responding connection,1760 responding to a unicast neighbor solicitation.1768 message. When responding to unicast solicitations, the option can be
103 recording, responding with VCON.
87 an I2C device was temporarily not responding, usually it
431 - When responding to linux-kernel email (or that on other lists) preserve434 sure that the person you are responding to is in the Cc: list. This443 text you are responding to). It makes your response harder to read and
284 - If you are responding to a bug report or a feature request, copy the
43 still responding before doing the write call to ping the watchdog.
177 responding to these types of bugs in a timely manner (especially during a
134 this means that the hardware is not responding to the driver's attempts
302 responsible for responding to this. If the subsystem has references to400 responsible for responding to the change.
425 Disable device from responding to MMIO/IO Port addresses490 4.6 Disable Device from responding to MMIO/IO Port addresses
11 the program inside the uC that is responding to calls.
192 not responding. Reasons for this may be:
404 to stop responding.
809 SPI slave handler responding with the time of reception of the last
969 Does nothing. Can be used to check if the firmware is responding.2215 is responding.
584 hard Retry file operations if server is not responding
