1 2<!-- Explain your changes here... --> 3 4---- 5## git request-pull output: 6``` 7<!-- START REPLACE ME --> 8 9Generate your PR shortlog and diffstat with these commands: 10 git remote add axboe-tree https://github.com/axboe/liburing 11 git fetch axboe-tree 12 git request-pull axboe-tree/master your_fork_URL your_branch_name 13 14Then replace this with the output of `git request-pull` command. 15 16<!-- END REPLACE ME --> 17``` 18---- 19<details> 20<summary>Click to show/hide pull request guidelines</summary> 21 22## Pull Request Guidelines 231. To make everyone easily filter pull request from the email 24notification, use `[GIT PULL]` as a prefix in your PR title. 25``` 26[GIT PULL] Your Pull Request Title 27``` 282. Follow the commit message format rules below. 293. Follow the Linux kernel coding style (see: https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst). 30 31### Commit message format rules: 321. The first line is title (don't be more than 72 chars if possible). 332. Then an empty line. 343. Then a description (may be omitted for truly trivial changes). 354. Then an empty line again (if it has a description). 365. Then a `Signed-off-by` tag with your real name and email. For example: 37``` 38Signed-off-by: Foo Bar <foo.bar@gmail.com> 39``` 40 41The description should be word-wrapped at 72 chars. Some things should 42not be word-wrapped. They may be some kind of quoted text - long 43compiler error messages, oops reports, Link, etc. (things that have a 44certain specific format). 45 46Note that all of this goes in the commit message, not in the pull 47request text. The pull request text should introduce what this pull 48request does, and each commit message should explain the rationale for 49why that particular change was made. The git tree is canonical source 50of truth, not github. 51 52Each patch should do one thing, and one thing only. If you find yourself 53writing an explanation for why a patch is fixing multiple issues, that's 54a good indication that the change should be split into separate patches. 55 56If the commit is a fix for an issue, add a `Fixes` tag with the issue 57URL. 58 59Don't use GitHub anonymous email like this as the commit author: 60``` 61123456789+username@users.noreply.github.com 62``` 63 64Use a real email address! 65 66### Commit message example: 67``` 68src/queue: don't flush SQ ring for new wait interface 69 70If we have IORING_FEAT_EXT_ARG, then timeouts are done through the 71syscall instead of by posting an internal timeout. This was done 72to be both more efficient, but also to enable multi-threaded use 73the wait side. If we touch the SQ state by flushing it, that isn't 74safe without synchronization. 75 76Fixes: https://github.com/axboe/liburing/issues/402 77Signed-off-by: Jens Axboe <axboe@kernel.dk> 78``` 79 80</details> 81 82---- 83## By submitting this pull request, I acknowledge that: 841. I have followed the above pull request guidelines. 852. I have the rights to submit this work under the same license. 863. I agree to a Developer Certificate of Origin (see https://developercertificate.org for more information). 87