| /linux/drivers/usb/class/ |
| H A D | cdc-wdm.c | 255 int responding; in wdm_int_callback() local
314 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_int_callback()
315 if (!desc->resp_count++ && !responding in wdm_int_callback()
988 int responding; in wdm_rxwork() local
994 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()
996 if (!responding) in wdm_rxwork()
|
| /linux/Documentation/admin-guide/nfs/ |
| H A D | pnfs-block-server.rst | 23 If the nfsd server needs to fence a non-responding client it calls
|
| /linux/drivers/scsi/mpt3sas/ |
| H A D | mpt3sas_base.h | 574 u8 responding; member
639 u8 responding; member
728 u8 responding; member
822 u8 responding; member
|
| H A D | mpt3sas_scsih.c | 10956 sas_device->responding = 1; in _scsih_mark_responding_sas_device()
11126 pcie_device->responding = 1; in _scsih_mark_responding_pcie_device()
11248 raid_device->responding = 1; in _scsih_mark_responding_raid_device()
11378 sas_expander->responding = 1; in _scsih_mark_responding_expander()
11485 if (!sas_device->responding) in _scsih_remove_unresponding_devices()
11488 sas_device->responding = 0; in _scsih_remove_unresponding_devices()
11516 if (!pcie_device->responding) in _scsih_remove_unresponding_devices()
11519 pcie_device->responding = 0; in _scsih_remove_unresponding_devices()
11534 if (!raid_device->responding) in _scsih_remove_unresponding_devices()
11538 raid_device->responding = 0; in _scsih_remove_unresponding_devices()
[all …]
|
| /linux/Documentation/networking/device_drivers/atm/ |
| H A D | cxacru.rst | 10 module loaded, the device will sometimes stop responding after unloading the
|
| /linux/drivers/bus/ |
| H A D | Kconfig | 49 not responding on timeout an IRQ is raised with an erroneous address
66 any bus protocol errors and device not responding situations by
|
| /linux/tools/memory-model/Documentation/ |
| H A D | README | 41 documented, especially when you are responding to complaints
|
| H A D | access-marking.txt | 55 when responding to KCSAN complaints. Churning the code base with
|
| /linux/Documentation/i2c/ |
| H A D | fault-codes.rst | 95 an I2C device was temporarily not responding, usually it
|
| /linux/Documentation/process/ |
| H A D | 2.Process.rst | 423 - When responding to linux-kernel email (or that on other lists) preserve
426 sure that the person you are responding to is in the Cc: list. This
436 the quoted text you are responding to.) For more details, see
|
| H A D | 5.Posting.rst | 326 - If you are responding to a bug report or a feature request, copy the
|
| /linux/Documentation/watchdog/ |
| H A D | watchdog-api.rst | 48 still responding before doing the write call to ping the watchdog.
|
| /linux/Documentation/filesystems/ |
| H A D | configfs.rst | 321 responsible for responding to this. If the subsystem has references to
424 responsible for responding to the change.
|
| /linux/Documentation/PCI/ |
| H A D | pci.rst | 372 - Disable device from responding to MMIO/IO Port addresses
437 Disable Device from responding to MMIO/IO Port addresses
|
| /linux/drivers/mailbox/ |
| H A D | Kconfig | 54 processer can write data in a channel, and set co-responding register
|
| /linux/Documentation/hwmon/ |
| H A D | abituguru-datasheet.rst | 12 the program inside the uC that is responding to calls.
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse.rst | 192 not responding. Reasons for this may be:
|
| /linux/Documentation/driver-api/surface_aggregator/ |
| H A D | ssh.rst | 144 the frame by responding with a message containing an |ACK|-type frame with
|
| /linux/Documentation/scsi/ |
| H A D | aic79xx.rst | 496 to stop responding.
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | cx2341x-devel.rst | 971 Does nothing. Can be used to check if the firmware is responding.
2217 is responding.
|
| /linux/Documentation/networking/ |
| H A D | ip-sysctl.rst | 585 tcp_keepalive_probes it is time to kill not responding connection,
3032 responding to a unicast neighbor solicitation.
3041 message. When responding to unicast solicitations, the option can be
|
| H A D | rxrpc.rst | 1058 the peer into responding, which would then cause the value returned by the
|
| /linux/Documentation/admin-guide/cifs/ |
| H A D | usage.rst | 690 Retry file operations if server is not responding
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 1347 Sometimes the maintainer might not be responding in a timely manner; other
|
| /linux/Documentation/virt/kvm/ |
| H A D | api.rst | 5664 event channel delivery, so responding within the kernel without
|