Searched refs:responding (Results 1 – 21 of 21) sorted by relevance
236 int responding; in wdm_int_callback() local290 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_int_callback()291 if (!responding && !test_bit(WDM_DISCONNECTING, &desc->flags) in wdm_int_callback()692 int responding; in wdm_rxwork() local698 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()700 if (!responding) in wdm_rxwork()
369 u8 responding; member407 u8 responding; member492 u8 responding; member
6646 sas_device->responding = 1; in _scsih_mark_responding_sas_device()6753 raid_device->responding = 1; in _scsih_mark_responding_raid_device()6872 sas_expander->responding = 1; in _scsih_mark_responding_expander()6950 if (sas_device->responding) { in _scsih_remove_unresponding_sas_devices()6951 sas_device->responding = 0; in _scsih_remove_unresponding_sas_devices()6971 if (raid_device->responding) { in _scsih_remove_unresponding_sas_devices()6972 raid_device->responding = 0; in _scsih_remove_unresponding_sas_devices()6988 if (sas_expander->responding) { in _scsih_remove_unresponding_sas_devices()6989 sas_expander->responding = 0; in _scsih_remove_unresponding_sas_devices()
4 module loaded, the device will sometimes stop responding after unloading the
262 tcp_keepalive_probes it is time to kill not responding connection,1246 responding to a unicast neighbor solicitation.1254 message. When responding to unicast solicitations, the option can be
103 recording, responding with VCON.
12 is responding.
9 Does nothing. Can be used to check if the firmware is responding.
90 an I2C device was temporarily not responding, usually it
415 - When responding to linux-kernel email (or that on other lists) preserve418 sure that the person you are responding to is in the Cc: list. This427 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
43 still responding before doing the write call to ping the watchdog.
268 responsible for responding to this. If the subsystem has references to376 responsible for responding to the change.
134 this means that the hardware is not responding to the driver's attempts
444 Disable device from responding to MMIO/IO Port addresses509 4.6 Disable Device from responding to MMIO/IO Port addresses
192 not responding. Reasons for this may be:
11 the program inside the uC that is responding to calls.
404 to stop responding.
495 assigned in the bus responding region (this will be used by the
585 hard Retry file operations if server is not responding
241 time out requests if server still responding reasonably fast