Searched refs:datagram (Results 1 – 11 of 11) sorted by relevance
69 EXPECT_EQ(msg.datagram, 0); in TEST()82 EXPECT_EQ(msg.datagram, 0); in TEST()93 EXPECT_EQ(msg.datagram, 1); in TEST()113 EXPECT_EQ(msg.datagram, 0); in TEST()126 EXPECT_EQ(msg.datagram, 0); in TEST()156 msg.datagram = 1; in TEST()162 msg.datagram = 0; in TEST()1264 EXPECT_EQ(request->hdr.datagram, 0); in TEST()1348 .datagram = 0, in TEST()1357 .datagram = 0, in TEST()[all …]
187 uint8_t datagram : 1; //!< Datagram bit member191 uint8_t datagram : 1; //!< Datagram bit
58 * Eat up the not-yet received datagram. Some systems insist on a
134 - void (*sink) (); /* datagram sink function or 0 */138 + void (*sink) (int); /* datagram sink function or 0 */
904 /* sock_sink - absorb unreceived IP datagram */
35 uint8_t datagram = (hdr->msg_type == PLDM_ASYNC_REQUEST_NOTIFY) ? 1 : 0; in pack_pldm_header_errno() local43 msg->datagram = datagram; in pack_pldm_header_errno()63 hdr->msg_type = msg->datagram ? PLDM_ASYNC_REQUEST_NOTIFY : in unpack_pldm_header_errno()
309 if (hdr && (hdr->request || hdr->datagram)) in receive()
295 # Configuration info for datagram socket chardevs.473 # @udp: datagram socket (since 1.5)573 # @data: Configuration info for datagram socket chardevs
795 # Configuration info for datagram socket netdev.
3999 datagram.c: 4449
3685 machine or a proxy using a datagram oriented unix domain socket.3708 machine or a proxy using a datagram oriented unix socket.3731 machine or a proxy using a datagram oriented socket file descriptor.