<!-- START REPLACE ME --> Generate your PR shortlog and diffstat with these commands: git remote add axboe-tree https://github.com/axboe/liburing git fetch axboe-tree git request-pull axboe-tree/master your_fork_URL your_branch_name Then replace this with the output of `git request-pull` command. <!-- END REPLACE ME -->
[GIT PULL]
as a prefix in your PR title.[GIT PULL] Your Pull Request Title
Signed-off-by
tag with your real name and email. For example:Signed-off-by: Foo Bar <foo.bar@gmail.com>
The description should be word-wrapped at 72 chars. Some things should not be word-wrapped. They may be some kind of quoted text - long compiler error messages, oops reports, Link, etc. (things that have a certain specific format).
Note that all of this goes in the commit message, not in the pull request text. The pull request text should introduce what this pull request does, and each commit message should explain the rationale for why that particular change was made. The git tree is canonical source of truth, not github.
Each patch should do one thing, and one thing only. If you find yourself writing an explanation for why a patch is fixing multiple issues, that's a good indication that the change should be split into separate patches.
If the commit is a fix for an issue, add a Fixes
tag with the issue URL.
Don't use GitHub anonymous email like this as the commit author:
123456789+username@users.noreply.github.com
Use a real email address!
src/queue: don't flush SQ ring for new wait interface If we have IORING_FEAT_EXT_ARG, then timeouts are done through the syscall instead of by posting an internal timeout. This was done to be both more efficient, but also to enable multi-threaded use the wait side. If we touch the SQ state by flushing it, that isn't safe without synchronization. Fixes: https://github.com/axboe/liburing/issues/402 Signed-off-by: Jens Axboe <axboe@kernel.dk>