Change in libosmocore[master]: socket: introduce osmo_sock_init3 & osmo_sock_init3_ofd

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

lynxis lazus gerrit-no-reply at lists.osmocom.org
Mon Aug 10 00:57:34 UTC 2020


lynxis lazus has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/19143 )

Change subject: socket: introduce osmo_sock_init3 & osmo_sock_init3_ofd
......................................................................


Patch Set 12:

> Patch Set 11:
> 
> > Patch Set 9:
> > 
> > doest it make sense to keep a completely separate implementation for osmo_sock_init2_ofd, rather than "redirecting" the old code to the new?
> 
> ping?

I don't think it's possible. While osmo_sock_init2 can take AF_UNSPEC, init3 can't. Also osmo_sock_init2 does name resolution, what init3 doesn't.


-- 
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/19143
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings

Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I1eece543e3241ef0e095eb63bb831f7c15a16794
Gerrit-Change-Number: 19143
Gerrit-PatchSet: 12
Gerrit-Owner: lynxis lazus <lynxis at fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: lynxis lazus <lynxis at fe80.eu>
Gerrit-Reviewer: pespin <pespin at sysmocom.de>
Gerrit-CC: laforge <laforge at osmocom.org>
Gerrit-Comment-Date: Mon, 10 Aug 2020 00:57:34 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20200810/cf0bf805/attachment.htm>


More information about the gerrit-log mailing list