[fprint] Planning libfprint API changes (2.x)
Benjamin Berg
benjamin at sipsolutions.net
Wed Jul 10 12:24:39 UTC 2019
Hey,
On Wed, 2019-07-10 at 14:21 +0200, Bastien Nocera wrote:
> > … Most drivers have been ported at this point (fixing a
> > number of issues in the process).
>
> Anything that could be backported? Failing that, an issue filed per
> problem would go a long way towards cleanups for 1.0.
There were a few places with e.g. large memory leaks or even things
that looked suspiciously like out of bounds memory writes.
Does it sound good to you if I create a private ticket for a start and
write down some of the major pain points (before I forget about where
it was again)?
Benjamin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/fprint/attachments/20190710/b3afab32/attachment.sig>
More information about the fprint
mailing list