/linux-6.12.1/net/tipc/ |
D | discover.c | 210 bool respond = false; in tipc_disc_rcv() local 251 &maddr, &respond, &dupl_addr); in tipc_disc_rcv() 254 if (!respond) in tipc_disc_rcv()
|
D | node.h | 96 bool *respond, bool *dupl_addr);
|
D | node.c | 1172 bool *respond, bool *dupl_addr) in tipc_node_check_dest() argument 1188 *respond = false; in tipc_node_check_dest() 1215 *respond = true; in tipc_node_check_dest() 1233 *respond = true; in tipc_node_check_dest() 1253 *respond = true; in tipc_node_check_dest() 1265 *respond = true; in tipc_node_check_dest() 1287 *respond = false; in tipc_node_check_dest()
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-bus-fsi-devices-sbefifo | 6 timeout; i.e. the SBE did not respond within the time allotted
|
D | sysfs-class-power-ltc4162l | 73 remain in this mode (and no longer respond to I2C commands)
|
/linux-6.12.1/drivers/usb/gadget/function/ |
D | f_hid.c | 888 goto respond; in hidg_setup() 896 goto respond; in hidg_setup() 906 goto respond; in hidg_setup() 921 goto respond; in hidg_setup() 931 goto respond; in hidg_setup() 949 goto respond; in hidg_setup() 957 goto respond; in hidg_setup() 978 respond: in hidg_setup()
|
/linux-6.12.1/Documentation/devicetree/bindings/rtc/ |
D | isil,isl12026.txt | 4 registers respond at bus address 0x6f, and the EEPROM array responds
|
/linux-6.12.1/Documentation/block/ |
D | null_blk.rst | 76 Whether or not to use a memory buffer to respond to IO requests 80 1 Use a memory buffer to respond to IO requests
|
/linux-6.12.1/drivers/net/wwan/iosm/ |
D | iosm_ipc_mux_codec.h | 280 size_t res_size, bool blocking, bool respond);
|
/linux-6.12.1/Documentation/i2c/ |
D | slave-testunit-backend.rst | 137 Partial command. This test will respond to a block process call as defined by 170 128 bytes. However, it will only respond if the read message is connected to 230 If the host does not respond to the alert within 1 second, the test will be
|
D | ten-bit-addresses.rst | 8 address 0x10 (though a single device could respond to both of them).
|
D | i2c-stub.rst | 16 quick commands to the specified addresses; it will respond to the other
|
/linux-6.12.1/Documentation/driver-api/xilinx/ |
D | eemi.rst | 17 device to issue or respond to power management requests.
|
/linux-6.12.1/drivers/media/usb/dvb-usb-v2/ |
D | dvbsky.c | 350 u8 command[4], respond[2], command_size, respond_size; in dvbsky_ci_ctrl() local 365 respond, respond_size); in dvbsky_ci_ctrl() 369 *mem = respond[1]; in dvbsky_ci_ctrl()
|
/linux-6.12.1/Documentation/process/ |
D | 6.Followthrough.rst | 44 impulse to respond in kind. Code review is about the code, not about 66 that the reviewer is asking you to fix. And respond back to the reviewer: 184 respond to these reports is a matter of basic pride in your work. If that 216 really only one way to respond: be pleased that your problem got solved and
|
/linux-6.12.1/Documentation/w1/masters/ |
D | omap-hdq.rst | 29 does not respond with a presence pulse as it does in the 1-Wire protocol.
|
/linux-6.12.1/Documentation/maintainer/ |
D | feature-and-driver-maintainers.rst | 34 reviewers should try to respond quicker than what is the usual patch 81 Maintainers furthermore should respond to reports about other kinds of
|
/linux-6.12.1/Documentation/driver-api/pldmfw/ |
D | index.rst | 66 the device. For each component, the firmware may respond with an
|
/linux-6.12.1/Documentation/scsi/ |
D | megaraid.rst | 10 Different classes of controllers from LSI Logic accept and respond to the
|
D | BusLogic.rst | 306 respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI 324 The BT-948/958/958D will not respond to any of the ISA compatible I/O ports 325 that previous BusLogic SCSI Host Adapters respond to. This driver supports 375 UltraSCSI operation, or where existing SCSI devices do not properly respond 500 respond correctly when Logical Units above 0 are addressed.
|
/linux-6.12.1/Documentation/input/devices/ |
D | alps.rst | 31 All ALPS touchpads should respond to the "E6 report" command sequence: 32 E8-E6-E6-E6-E9. An ALPS touchpad should respond with either 00-00-0A or 53 EC-EC-EC-E9 places the device in command mode, and the device will respond
|
/linux-6.12.1/Documentation/usb/ |
D | raw-gadget.rst | 25 descriptors. Note that the UDC driver might respond to some requests on
|
/linux-6.12.1/Documentation/filesystems/ |
D | befs.rst | 34 respond to the address given above...
|
/linux-6.12.1/Documentation/networking/ |
D | mctp.rst | 174 may only respond (with TO=0) to requests they have received. 213 sent (TO=1) and may only respond (TO=0) to requests they have received.
|
/linux-6.12.1/Documentation/hid/ |
D | uhid.rst | 49 register the device. UHID will respond with a UHID_START event. You can now 176 parallel. However, if you fail to respond with a UHID_GET_REPORT_REPLY, the
|