Searched refs:responding (Results 1 – 22 of 22) sorted by relevance
213 int responding; in wdm_int_callback() local272 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_int_callback()273 if (!desc->resp_count++ && !responding in wdm_int_callback()733 int responding; in wdm_rxwork() local739 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()741 if (!responding) in wdm_rxwork()
21 If the nfsd server needs to fence a non-responding client it calls
4 module loaded, the device will sometimes stop responding after unloading the
334 tcp_keepalive_probes it is time to kill not responding connection,1586 responding to a unicast neighbor solicitation.1594 message. When responding to unicast solicitations, the option can be
468 u8 responding; member527 u8 responding; member612 u8 responding; member
6821 sas_device->responding = 1; in _scsih_mark_responding_sas_device()6946 raid_device->responding = 1; in _scsih_mark_responding_raid_device()7070 sas_expander->responding = 1; in _scsih_mark_responding_expander()7159 if (!sas_device->responding) in _scsih_remove_unresponding_sas_devices()7162 sas_device->responding = 0; in _scsih_remove_unresponding_sas_devices()7181 if (!raid_device->responding) in _scsih_remove_unresponding_sas_devices()7185 raid_device->responding = 0; in _scsih_remove_unresponding_sas_devices()7196 if (!sas_expander->responding) in _scsih_remove_unresponding_sas_devices()7199 sas_expander->responding = 0; in _scsih_remove_unresponding_sas_devices()
103 recording, responding with VCON.
87 an I2C device was temporarily not responding, usually it
12 is responding.
9 Does nothing. Can be used to check if the firmware is responding.
411 - When responding to linux-kernel email (or that on other lists) preserve414 sure that the person you are responding to is in the Cc: list. This423 text you are responding to). It makes your response harder to read and
267 - If you are responding to a bug report or a feature request, copy the
169 responding to these types of bugs in a timely manner (especially during a
43 still responding before doing the write call to ping the watchdog.
262 responsible for responding to this. If the subsystem has references to360 responsible for responding to the change.
134 this means that the hardware is not responding to the driver's attempts
426 Disable device from responding to MMIO/IO Port addresses491 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.
585 hard Retry file operations if server is not responding
241 time out requests if server still responding reasonably fast