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/.
Hoernchen gerrit-no-reply at lists.osmocom.orgHoernchen has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/25413 ) Change subject: vty: allow flushing ...................................................................... Patch Set 2: You have more than one thread, one owns the vty an related talloc contexts, the other one does not, but the other one would like to (or rather has to due to libosmocore design) print something on the vty so that other thread has to block the main thread while acessing the vty context and due to the internal buffer handling with talloc instead of threadsafe plain old malloc there might be a mix of different allocation contexts that are not thread safe so the second thread has to ensure the vty output is flushed before unblocking the main thread. Or someone somewhere might just want to flush the damn vty without writing a book about it. -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/25413 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: If984b9ad2eba9f400bc29a7aa8825e241fd1d2a9 Gerrit-Change-Number: 25413 Gerrit-PatchSet: 2 Gerrit-Owner: Hoernchen <ewild at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Reviewer: pespin <pespin at sysmocom.de> Gerrit-Comment-Date: Fri, 10 Sep 2021 14:31:30 +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/20210910/4ca84cec/attachment.htm>