From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Pavel Begunkov <[email protected]>,
Gilang Fachrezy <[email protected]>,
Muhammad Rizki <[email protected]>,
VNLX Kernel Department <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
io-uring Mailing List <[email protected]>
Subject: Re: [PATCH liburing v1 0/8] liburing updates
Date: Mon, 19 Dec 2022 10:00:26 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 19 Dec 2022 22:49:52 +0700, Ammar Faizi wrote:
> liburing updates, there are 8 patches in this series:
>
> - Patch #1 is to add a missing SPDX-License-Idetifier.
> - Patch #2 is a Makefile warning fix due to the recent liburing
> version check feature.
> - Patch #3 to #6 are a preparation patch to make the clang build
> stricter.
> - Patch #7 is to apply extra clang flags to the GitHub bot CI.
> - Patch #8 is the CHANGELOG file update.
>
> [...]
Applied, thanks!
[1/8] ffi: Add SPDX-License-Idetifier
(no commit info)
[2/8] Makefile: Add a '+' char to silence a Makefile warning
(no commit info)
[3/8] tests: Fix `-Wstrict-prototypes` warnings from Clang
(no commit info)
[4/8] test/ring-leak: Remove a "break" statement in a "for loop"
(no commit info)
[5/8] tests: Fix clang `-Wunreachable-code` warning
(no commit info)
[6/8] tests: Declare internal variables as static
(no commit info)
[7/8] github: Add more extra flags for clang build
(no commit info)
[8/8] CHANGELOG: Update the CHANGELOG file
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-12-19 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 15:49 [PATCH liburing v1 0/8] liburing updates Ammar Faizi
2022-12-19 15:49 ` [PATCH liburing v1 1/8] ffi: Add SPDX-License-Idetifier Ammar Faizi
2022-12-19 15:49 ` [PATCH liburing v1 2/8] Makefile: Add a '+' char to silence a Makefile warning Ammar Faizi
2022-12-19 15:49 ` [PATCH liburing v1 3/8] tests: Fix `-Wstrict-prototypes` warnings from Clang Ammar Faizi
2022-12-19 15:49 ` [PATCH liburing v1 4/8] test/ring-leak: Remove a "break" statement in a "for loop" Ammar Faizi
2022-12-19 15:49 ` [PATCH liburing v1 5/8] tests: Fix clang `-Wunreachable-code` warning Ammar Faizi
2022-12-19 15:49 ` [PATCH liburing v1 6/8] tests: Declare internal variables as static Ammar Faizi
2022-12-19 15:49 ` [PATCH liburing v1 7/8] github: Add more extra flags for clang build Ammar Faizi
2022-12-19 15:50 ` [PATCH liburing v1 8/8] CHANGELOG: Update the CHANGELOG file Ammar Faizi
2022-12-19 17:00 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=167146922615.37948.17402262848405700296.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox