Lines Matching refs:connect
164 * For example, bind() and connect() won't reset sk->sk_err,
645 * Now, check all discovered devices (if any), and connect
959 * The main difference with a "standard" connect is that with IrDA we need
962 * Because of this service name resoltion, we can offer "auto-connect",
963 * where we connect to a service without specifying a destination address.
968 * o EBUSY : already processing a connect
971 * o ENOTUNIQ : more than one node has addr->sir_name (auto-connect)
972 * o ENETUNREACH : no node found on the network (auto-connect)
985 /* Don't allow connect for Ultra sockets */
1018 IRDA_DEBUG(0, "%s(), auto-connect failed!\n", __func__);
1027 * user want to connect on a specific LSAP. Prevent
1034 IRDA_DEBUG(0, "%s(), connect failed!\n", __func__);
1038 /* Directly connect to the remote LSAP
1059 IRDA_DEBUG(0, "%s(), connect failed!\n", __func__);
1260 * 1) This may include IAS request, both in connect and getsockopt.
2396 * to connect and/or may not have a valid service name
2486 * up the caller, so that he has time to connect to it before
2591 .connect = irda_connect,
2615 .connect = irda_connect,
2639 .connect = irda_connect,
2664 .connect = sock_no_connect,