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/OpenBSC@lists.osmocom.org/.
Ruben Undheim ruben.undheim at gmail.comHi, > -- ERROR sending ciphering mode command: rc=-95 > +- ERROR sending ciphering mode command: rc=-122 > > i.e. a mismatching rc gets returned. It's not an error with any practical > effect. > > Aha, could it simply be that the errno are defined differently on this > platform? It should be -95 == -ENOTSUP, while we get -122. I will have a look. Thanks for the hint. :D > > Interesting. I did not know about this way of viewing the patches, > > although I am behind most of the patches. Please just pull back > > whatever you find useful. > > Ideally, the patch author goes on to submit it on gerrit.osmocom.org :) Yes, ideally! I have actually done it on gerrit to you guys once before [1]. However, I am interacting with so many different upstream, and everyone has their own way of doing things. Therefore I prefer to just write an email or file an issue, and you can just pick whatever you want. Since you deal with gerrit regularly, it will be much more efficient. (I only have github and salsa in my fingers..) Many patches are not relevant for upstream either. Only when making real bug-fixes (like now for big-endian archs), it makes sense for me to spend time getting them into gerrit myself (and waste time learning how to do it again :D ). Best regards Ruben [1] http://lists.osmocom.org/pipermail/openbsc/2016-May/thread.html#9132