From: Jens Axboe <[email protected]>
To: Bart Van Assche <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH liburing 0/3] Three small liburing patches
Date: Sun, 21 Jun 2020 20:50:43 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/21/20 2:36 PM, Bart Van Assche wrote:
> Hi Jens,
>
> The changes in this patch series are as follows:
> - Enable additional compiler warnings, similar to W=1 for kernel code.
> - Simplify the barrier.h header file.
> - Convert a macro into an inline function to allow compilers to produce
> better diagnostics.
>
> Please consider this patch series for the official liburing repository.
Thanks, applied.
--
Jens Axboe
prev parent reply other threads:[~2020-06-22 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 20:36 [PATCH liburing 0/3] Three small liburing patches Bart Van Assche
2020-06-21 20:36 ` [PATCH liburing 1/3] Makefiles: Enable -Wextra Bart Van Assche
2020-06-21 20:36 ` [PATCH liburing 2/3] src/include/liburing/barrier.h: Use C11 atomics Bart Van Assche
2020-06-21 20:36 ` [PATCH liburing 3/3] Convert __io_uring_get_sqe() from a macro into an inline function Bart Van Assche
2020-06-22 2:50 ` 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 \
[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