| /linux-4.1.27/drivers/usb/class/ |
| D | cdc-wdm.c | 213 int responding; in wdm_int_callback() local
272 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() local
739 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()
741 if (!responding) in wdm_rxwork()
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | pnfs-block-server.txt | 21 If the nfsd server needs to fence a non-responding client it calls
|
| /linux-4.1.27/drivers/scsi/mpt2sas/ |
| D | mpt2sas_base.h | 377 u8 responding; member
416 u8 responding; member
501 u8 responding; member
|
| D | mpt2sas_scsih.c | 6713 sas_device->responding = 1; in _scsih_mark_responding_sas_device()
6820 raid_device->responding = 1; in _scsih_mark_responding_raid_device()
6944 sas_expander->responding = 1; in _scsih_mark_responding_expander()
7027 if (!sas_device->responding) in _scsih_remove_unresponding_sas_devices()
7031 sas_device->responding = 0; in _scsih_remove_unresponding_sas_devices()
7040 if (!raid_device->responding) in _scsih_remove_unresponding_sas_devices()
7044 raid_device->responding = 0; in _scsih_remove_unresponding_sas_devices()
7054 if (!sas_expander->responding) in _scsih_remove_unresponding_sas_devices()
7057 sas_expander->responding = 0; in _scsih_remove_unresponding_sas_devices()
|
| /linux-4.1.27/drivers/scsi/mpt3sas/ |
| D | mpt3sas_base.h | 315 u8 responding; member
346 u8 responding; member
425 u8 responding; member
|
| D | mpt3sas_scsih.c | 6382 sas_device->responding = 1; in _scsih_mark_responding_sas_device()
6487 raid_device->responding = 1; in _scsih_mark_responding_raid_device()
6602 sas_expander->responding = 1; in _scsih_mark_responding_expander()
6685 if (!sas_device->responding) in _scsih_remove_unresponding_sas_devices()
6689 sas_device->responding = 0; in _scsih_remove_unresponding_sas_devices()
6698 if (!raid_device->responding) in _scsih_remove_unresponding_sas_devices()
6702 raid_device->responding = 0; in _scsih_remove_unresponding_sas_devices()
6713 if (!sas_expander->responding) in _scsih_remove_unresponding_sas_devices()
6716 sas_expander->responding = 0; in _scsih_remove_unresponding_sas_devices()
|
| /linux-4.1.27/Documentation/networking/ |
| D | cxacru.txt | 4 module loaded, the device will sometimes stop responding after unloading the
|
| D | ip-sysctl.txt | 325 tcp_keepalive_probes it is time to kill not responding connection,
1506 responding to a unicast neighbor solicitation.
1514 message. When responding to unicast solicitations, the option can be
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.audio | 103 recording, responding with VCON.
|
| /linux-4.1.27/Documentation/i2c/ |
| D | fault-codes | 87 an I2C device was temporarily not responding, usually it
|
| /linux-4.1.27/Documentation/video4linux/cx2341x/ |
| D | fw-decoder-api.txt | 12 is responding.
|
| D | fw-encoder-api.txt | 9 Does nothing. Can be used to check if the firmware is responding.
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 2.Process | 411 - When responding to linux-kernel email (or that on other lists) preserve
414 sure that the person you are responding to is in the Cc: list. This
423 text you are responding to). It makes your response harder to read and
|
| D | 5.Posting | 267 - If you are responding to a bug report or a feature request, copy the
|
| /linux-4.1.27/ |
| D | REPORTING-BUGS | 169 responding to these types of bugs in a timely manner (especially during a
|
| /linux-4.1.27/Documentation/watchdog/ |
| D | watchdog-api.txt | 43 still responding before doing the write call to ping the watchdog.
|
| /linux-4.1.27/Documentation/filesystems/configfs/ |
| D | configfs.txt | 268 responsible for responding to this. If the subsystem has references to
376 responsible for responding to the change.
|
| /linux-4.1.27/Documentation/ide/ |
| D | ide.txt | 134 this means that the hardware is not responding to the driver's attempts
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci.txt | 426 Disable device from responding to MMIO/IO Port addresses
491 4.6 Disable Device from responding to MMIO/IO Port addresses
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | fuse.txt | 192 not responding. Reasons for this may be:
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | abituguru-datasheet | 11 the program inside the uC that is responding to calls.
|
| /linux-4.1.27/Documentation/scsi/ |
| D | aic79xx.txt | 404 to stop responding.
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | README | 585 hard Retry file operations if server is not responding
|
| D | CHANGES | 241 time out requests if server still responding reasonably fast
|