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()753 int responding; in wdm_rxwork() local759 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()761 if (!responding) in wdm_rxwork()
21 If the nfsd server needs to fence a non-responding client it calls
540 u8 responding; member599 u8 responding; member687 u8 responding; member773 u8 responding; member
8403 sas_device->responding = 1; in _scsih_mark_responding_sas_device()8575 pcie_device->responding = 1; in _scsih_mark_responding_pcie_device()8697 raid_device->responding = 1; in _scsih_mark_responding_raid_device()8823 sas_expander->responding = 1; in _scsih_mark_responding_expander()8915 if (!sas_device->responding) in _scsih_remove_unresponding_devices()8918 sas_device->responding = 0; in _scsih_remove_unresponding_devices()8936 if (!pcie_device->responding) in _scsih_remove_unresponding_devices()8939 pcie_device->responding = 0; in _scsih_remove_unresponding_devices()8954 if (!raid_device->responding) in _scsih_remove_unresponding_devices()8958 raid_device->responding = 0; in _scsih_remove_unresponding_devices()[all …]
4 module loaded, the device will sometimes stop responding after unloading the
382 tcp_keepalive_probes it is time to kill not responding connection,1857 responding to a unicast neighbor solicitation.1865 message. When responding to unicast solicitations, the option can be
1039 the peer into responding, which would then cause the value returned by the
91 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
289 - If you are responding to a bug report or a feature request, copy the
177 responding to these types of bugs in a timely manner (especially during a
48 still responding before doing the write call to ping the watchdog.
142 this means that the hardware is not responding to the driver's attempts
371 - Disable device from responding to MMIO/IO Port addresses436 Disable Device from responding to MMIO/IO Port addresses
302 responsible for responding to this. If the subsystem has references to400 responsible for responding to the change.
192 not responding. Reasons for this may be:
12 the program inside the uC that is responding to calls.
404 to stop responding.
936 SPI slave handler responding with the time of reception of the last
971 Does nothing. Can be used to check if the firmware is responding.2217 is responding.
689 Retry file operations if server is not responding
