Home
last modified time | relevance | path

Searched refs:responding (Results 1 – 23 of 23) sorted by relevance

/linux/drivers/usb/class/
H A Dcdc-wdm.c250 int responding; in wdm_int_callback() local
309 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_int_callback()
310 if (!desc->resp_count++ && !responding in wdm_int_callback()
980 int responding; in wdm_rxwork() local
986 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()
988 if (!responding) in wdm_rxwork()
/linux/Documentation/admin-guide/nfs/
H A Dpnfs-block-server.rst23 If the nfsd server needs to fence a non-responding client it calls
/linux/Documentation/networking/device_drivers/atm/
H A Dcxacru.rst10 module loaded, the device will sometimes stop responding after unloading the
/linux/drivers/scsi/mpt3sas/
H A Dmpt3sas_base.h572 u8 responding; member
635 u8 responding; member
724 u8 responding; member
818 u8 responding; member
H A Dmpt3sas_scsih.c9722 sas_device->responding = 1; in _scsih_mark_responding_sas_device()
9892 pcie_device->responding = 1; in _scsih_mark_responding_pcie_device()
10014 raid_device->responding = 1; in _scsih_mark_responding_raid_device()
10144 sas_expander->responding = 1; in _scsih_mark_responding_expander()
10251 if (!sas_device->responding) in _scsih_remove_unresponding_devices()
10254 sas_device->responding = 0; in _scsih_remove_unresponding_devices()
10282 if (!pcie_device->responding) in _scsih_remove_unresponding_devices()
10285 pcie_device->responding = 0; in _scsih_remove_unresponding_devices()
10300 if (!raid_device->responding) in _scsih_remove_unresponding_devices()
10304 raid_device->responding = 0; in _scsih_remove_unresponding_devices()
[all …]
/linux/drivers/bus/
H A DKconfig49 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 DREADME38 documented, especially when you are responding to complaints
H A Daccess-marking.txt55 when responding to KCSAN complaints. Churning the code base with
/linux/Documentation/i2c/
H A Dfault-codes.rst95 an I2C device was temporarily not responding, usually it
/linux/Documentation/process/
H A D2.Process.rst426 - When responding to linux-kernel email (or that on other lists) preserve
429 sure that the person you are responding to is in the Cc: list. This
439 the quoted text you are responding to.) For more details, see
/linux/Documentation/watchdog/
H A Dwatchdog-api.rst48 still responding before doing the write call to ping the watchdog.
/linux/Documentation/filesystems/
H A Dconfigfs.rst321 responsible for responding to this. If the subsystem has references to
424 responsible for responding to the change.
H A Dfuse.rst178 not responding. Reasons for this may be:
/linux/Documentation/PCI/
H A Dpci.rst372 - Disable device from responding to MMIO/IO Port addresses
437 Disable Device from responding to MMIO/IO Port addresses
/linux/Documentation/hwmon/
H A Dabituguru-datasheet.rst12 the program inside the uC that is responding to calls.
/linux/Documentation/driver-api/surface_aggregator/
H A Dssh.rst144 the frame by responding with a message containing an |ACK|-type frame with
/linux/Documentation/scsi/
H A Daic79xx.rst496 to stop responding.
/linux/Documentation/driver-api/media/drivers/
H A Dcx2341x-devel.rst971 Does nothing. Can be used to check if the firmware is responding.
2217 is responding.
/linux/Documentation/networking/
H A Dip-sysctl.rst519 tcp_keepalive_probes it is time to kill not responding connection,
2654 responding to a unicast neighbor solicitation.
2663 message. When responding to unicast solicitations, the option can be
H A Drxrpc.rst1061 the peer into responding, which would then cause the value returned by the
/linux/Documentation/admin-guide/cifs/
H A Dusage.rst688 Retry file operations if server is not responding
/linux/Documentation/admin-guide/
H A Dreporting-issues.rst1347 Sometimes the maintainer might not be responding in a timely manner; other
/linux/Documentation/virt/kvm/
H A Dapi.rst5614 event channel delivery, so responding within the kernel without