Searched full:announced (Results 1 – 25 of 96) sorted by relevance
1234
26 ANNOUNCED=${MPTCP_LIB_EVENT_ANNOUNCED}367 verify_announce_event $server_evts $ANNOUNCED $server4_token "10.0.2.2" $client_addr_id \376 verify_announce_event "$server_evts" "$ANNOUNCED" "$server6_token" "dead:beef:2::2"\386 verify_announce_event "$server_evts" "$ANNOUNCED" "$server4_token" "10.0.2.2"\397 verify_announce_event "$client_evts" "$ANNOUNCED" "$client4_token" "10.0.2.1"\406 verify_announce_event "$client_evts" "$ANNOUNCED" "$client6_token" "dead:beef:2::1"\416 verify_announce_event "$client_evts" "$ANNOUNCED" "$client4_token" "10.0.2.1"\842 verify_announce_event "$client_evts" "$ANNOUNCED" "$client6_token" "10.0.2.1"\
7 module was already announced to become obsolete years ago.
3 that I have not really announced it yet). It was created by Larry Ewing,
25 the subnode to rpmsg device announced by SCP.
103 the subnode to rpmsg device announced by SCP.
574 * @num_vlan: number of announced VLANs. In the TVLV this struct is followed by575 * one batadv_tvlv_tt_vlan_data object per announced vlan623 * @flags: multicast flags announced by the orig node
59 * but has not been announced yet72 * part of the network but no node has already announced it
148 * A new address has been announced by the peer.
572 * @num_vlan: number of announced VLANs. In the TVLV this struct is followed by573 * one batadv_tvlv_tt_vlan_data object per announced vlan621 * @flags: multicast flags announced by the orig node
74 server channel that is announced (values are either
1352 * @bintval: beacon interval announced by discovered BSS.1354 * @bssid: BSSID announced by discovered BSS.1355 * @ssid_len: length of SSID announced by BSS.1356 * @ssid: SSID announced by discovered BSS.1357 * @payload: IEs that are announced by discovered BSS in its MGMt frames.1420 * @ssid: SSID announced by BSS
10 # and responder, i.e. TCPMSS announced values are too large and will still82 # ns2 is going via nsr2 with a smaller mtu, so that TCPMSS announced by both peers
66 device. Used to match the subnode to the rpmsg device announced by
22 reconfiguration sequence is a broadcast message announced to all devices)
32 * @SLIM_DEVICE_STATUS_UP: Slim device is announced on the bus.
157 * failures before we have announced that pinning is in loadpin_check()
91 we don't need to renegotiate the announced format */ in vv6410_init_controls()