Searched refs:reply (Results 1 – 25 of 35) sorted by relevance
12
| /Documentation/w1/ |
| D | w1.netlink | 68 command request. One reply is generated exactly for one w1_netlink_cmd
69 read request. Replies are not combined when sent - i.e. typical reply
100 reply:
126 structure) will be 'acked' by the w1 core. Format of the reply is the same
132 If reply is generated for master or root command (which do not have
133 w1_netlink_cmd attached), reply will contain only cn_msg and w1_netlink_msg
142 Status reply is generated for every w1_netlink_cmd embedded in the
144 reply will be generated for the w1_netlink_msg.
161 If command requires reply (like read command) it is sent on command completion.
176 Sequence number for reply is the same as was in request, and
|
| /Documentation/connector/ |
| D | ucon.c | 116 struct nlmsghdr *reply; in main() local
228 reply = (struct nlmsghdr *)buf; in main()
230 switch (reply->nlmsg_type) { in main()
236 data = (struct cn_msg *)NLMSG_DATA(reply); in main()
|
| D | connector.txt | 107 If you expect a reply to the message, then the sequence number in the
|
| /Documentation/ABI/testing/ |
| D | debugfs-olpc | 11 CC is the (hex) command, N is the count of expected reply bytes, and A A A A
15 a command. Hex reply bytes will be returned, *whether or not* they came from
|
| /Documentation/i2o/ |
| D | ioctl | 147 ETIMEDOUT Timeout waiting for reply message
184 ETIMEDOUT Timeout waiting for reply message
229 ETIMEDOUT Timeout waiting for reply message
271 ETIMEDOUT Timeout waiting for reply message
308 ETIMEDOUT Timeout waiting for reply message
330 ETIMEDOUT Timeout waiting for reply message
343 void *resbuf; /* Buffer for reply HTML page */
344 u32 *reslen; /* Length in bytes of reply buffer */
357 should be set to NULL. The actual size of the reply received is written
369 ETIMEDOUT Timeout waiting for reply message
|
| /Documentation/networking/ |
| D | rxrpc.txt | 58 receives a blob (the reply), and the server receives the request and then
59 transmits the reply.
125 which the service receives; then the service transmits the reply data
153 (*) Reception of a reply data packet implicitly hard-ACK's all the data
156 (*) An call is complete when the request has been sent, the reply has been
157 received and the final hard-ACK on the last packet of the reply has
211 followed by the reply being received with one or more recvmsgs.
234 the reply is transmitted with one or more sendmsgs, and then the final ACK
547 (6) The reply data will then be posted to the server socket for recvmsg() to
548 pick up. MSG_MORE will be flagged by recvmsg() if there's more reply data
[all …]
|
| D | nfc.txt | 95 all targets found by such device. Each reply message has target attributes with
|
| D | ip-sysctl.txt | 26 Controls the fwmark of kernel-generated IPv4 reply packets that are not
977 with the hope we will receive reply for our request and
989 0 - (default): reply for any local target IP address, configured
991 1 - reply only if the target IP address is local address
993 2 - reply only if the target IP address is local address
996 3 - do not reply for local addresses configured with scope host,
999 8 - do not reply for all local addresses
1110 Controls the fwmark of kernel-generated IPv6 reply packets that are not
|
| /Documentation/blockdev/ |
| D | nbd.txt | 6 request over TCP to the server, which will reply with the data read.
|
| D | paride.txt | 408 the list manager is a robot that will subscribe you using the reply
|
| /Documentation/filesystems/ |
| D | fuse.txt | 170 or may honor them by sending a reply to the _original_ request, with
184 should reply to the INTERRUPT request with an EAGAIN error. In case
186 reply will be ignored.
402 | | [create reply header before addr]
|
| D | coda.txt | 223 finishes with a reply to the kernel's VFS. Finally the VFS layer
284 reply from Venus, there is a field for the size of the reply. A flags
315 +o the message is a reply for a suspended thread P. If so it removes
320 processing its upcall with the data buffer replaced with the reply
1415 EErrrroorrss No reply is given.
|
| D | gfs2-glocks.txt | 224 reply that is received:
|
| /Documentation/scsi/ |
| D | arcmsr_spec.txt | 42 ** (outbount queue port) Request reply
44 ** => flag for reply
46 ** => real address (bit27--bit31) of reply arcmsr_cdb
47 ** bit31 : must be 0 (for this type of reply)
|
| /Documentation/ |
| D | pi-futex.txt | 22 The short reply: user-space PI helps achieving/improving determinism for
28 The longer reply:
|
| D | HOWTO | 399 reason, or don't reply only to the list address. Get used to receiving the
404 keep the "John Kernelhacker wrote ...:" lines at the top of your reply, and
|
| /Documentation/filesystems/pohmelfs/ |
| D | info.txt | 25 Number of milliseconds to wait for reply from remote server for data reading command.
|
| /Documentation/filesystems/nfs/ |
| D | nfsroot.txt | 139 and using the device that received the first reply.
144 to reply is used.
|
| D | nfs41-server.txt | 190 ca_maxrequestsize request and a ca_maxresponsesize reply, so we may
|
| /Documentation/video4linux/ |
| D | soc-camera.txt | 130 Therefore all camera drivers shall reply to .g_fmt() requests with their current
|
| /Documentation/input/ |
| D | iforce-protocol.txt | 160 The device should reply with the same packet plus two additional bytes
|
| /Documentation/development-process/ |
| D | 5.Posting | 303 sent as a reply to the first part so that they all thread together at the
306 are using git, please stay away from the --chain-reply-to option to avoid
|
| /Documentation/watchdog/ |
| D | watchdog-api.txt | 193 WDIOF_KEEPALIVEPING Keep alive ping reply
|
| /Documentation/s390/ |
| D | monreader.txt | 168 EIO: reply failed, read data is invalid and the application
|
| /Documentation/isdn/ |
| D | INTERFACE.CAPI | 147 appropriate reply message.
|
12