public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Dylan Yudaken <[email protected]>,
	io-uring Mailing List <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	Pavel Begunkov <[email protected]>,
	Facebook Kernel Team <[email protected]>
Subject: Re: [PATCH liburing v2 0/3] Clean up clang `-Wshorten-64-to-32` warnings
Date: Thu, 20 Oct 2022 07:11:02 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Thu, 20 Oct 2022 20:14:52 +0700, Ammar Faizi wrote:
> From: Ammar Faizi <[email protected]>
> 
> Hi Jens,
> 
> This is a v2.
> 
> v2:
>   - Fix Signed-off-by tag.
>   - Make the cast in patch #1 consistent.
> 
> [...]

Applied, thanks!

[1/3] liburing: Clean up `-Wshorten-64-to-32` warnings from clang
      commit: b9df4750ce9335437a34fd93c76863d871b70416
[2/3] Makefile: Introduce `LIBURING_CFLAGS` variable
      commit: 1755faf1737d0d84775aa46dd0a2b4b2e3474d28
[3/3] github: Append `-Wshorten-64-to-32` flag for clang build
      commit: 80817b7cd56b96a095c3cb4583a357d16fb867f1

Best regards,
-- 
Jens Axboe



      parent reply	other threads:[~2022-10-20 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 13:14 [PATCH liburing v2 0/3] Clean up clang `-Wshorten-64-to-32` warnings Ammar Faizi
2022-10-20 13:14 ` [PATCH liburing v2 1/3] liburing: Clean up `-Wshorten-64-to-32` warnings from clang Ammar Faizi
2022-10-20 13:14 ` [PATCH liburing v2 2/3] Makefile: Introduce `LIBURING_CFLAGS` variable Ammar Faizi
2022-10-20 13:14 ` [PATCH liburing v2 3/3] github: Append `-Wshorten-64-to-32` flag for clang build Ammar Faizi
2022-10-20 14:11 ` 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=166627506217.167739.6624404748025563028.b4-ty@kernel.dk \
    [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