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/.
laforge gerrit-no-reply at lists.osmocom.orglaforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-e1d/+/19041 ) Change subject: introduce notion of 'driver' ...................................................................... Patch Set 2: > I'm just wondering if a "type" is enough or if it should be struct with function pointers to the various operations / handlers for that driver. if you want to build a plugin architecture with an ABI, you need the function dispatch (e1_driver_ops). As long a we don't know how those drivers look like, we can either live with compiled-in drivers, they can be handled by switch() statements. I prefer to introduce infrastructure "as we go" and hence started simple. -- To view, visit https://gerrit.osmocom.org/c/osmo-e1d/+/19041 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-e1d Gerrit-Branch: master Gerrit-Change-Id: Ic168e25f2622b397bac2c133ec35f4a0a38f859b Gerrit-Change-Number: 19041 Gerrit-PatchSet: 2 Gerrit-Owner: laforge <laforge at osmocom.org> Gerrit-Assignee: tnt <tnt at 246tNt.com> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Reviewer: pespin <pespin at sysmocom.de> Gerrit-Reviewer: tnt <tnt at 246tNt.com> Gerrit-Comment-Date: Mon, 29 Jun 2020 15:26:24 +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/20200629/d59e135b/attachment.htm>