Commit graph

4 commits

Author SHA1 Message Date
Austin Seipp 0ca30f22f1
liburing: 1.0.0pre116 -> 1.0.0pre118
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-23 14:32:18 -05:00
Austin Seipp 4fe57ed90b
liburing: 1.0.0pre92 -> 1.0.0pre116
Notably, this includes non-x86 platform support, eventfd registration
for completion events, "drained" events that must have all outstanding
prior events/further events drained (e.g. for fsync), and linked CQEs
that can express completion ordering dependencies.

Most of these require 5.2-rc1, and linked CQEs require custom patches
from Jens' linux-block tree (that didn't hit the 5.2 merge window,
apparently.)

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-21 10:38:39 -05:00
Austin Seipp 0d2b66dff2
liburing: bump, fix version (1.0.0pre92_7b989f3)
I accidentally got the number of commits wrong in the previous
prerelease version string. This is now fixed.

Generally, this would result in functions like builtins.compareVersions
to give incorrect results, so 'nix-env -u' doesn't work. But I'm
justifying it here, because: most people use it as a library, so the
hash change is all that matters. Plus, I only authored this a week or
so ago in upstream, so this change is fast enough that I think people
will be fine with it and can work around, especially since it's
unreleased in any stable channel.

This also bumps the library to the newest version, which contains some
bugfixes, and now installs the manpages into the $man output for us.

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-02 19:32:05 -05:00
Austin Seipp 52714f495c
liburing: init at 1.0.0pre821_39e0ebd
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-04-22 11:18:18 -05:00