GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Alviro Iskandar Setiawan <[email protected]>,
	io-uring Mailing List <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>
Subject: Re: [GIT PULL] Upgrade to clang-17 (for liburing's CI)
Date: Wed, 1 Feb 2023 20:09:45 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 2/1/23 11:30 AM, Ammar Faizi wrote:
> Hi Jens,
> 
> clang-17 is now available. Upgrade the clang version in the liburing's
> CI to clang-17.
> 
> Two prep patches to address `-Wextra-semi-stmt` warnings:
> 
>   - Remove unnecessary semicolon (Alviro)
> 
>   - Wrap the CHECK() macro with a do-while statement (Alviro)
> 
> A patch for the CI:
> 
>   - Upgrade the clang version to 17 and append -Wextra-semi-stmt (me)
> 
> Please pull!
> 
> The following changes since commit 313aece03ab7dc7447a19cff5b5f542d0c1b2a1e:
> 
>   multicqes_drain: make trigger event wait before reading (2023-01-30 09:26:42 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/ammarfaizi2/liburing.git tags/upgrade-to-clang17-2023-02-02
> 
> for you to fetch changes up to c1b65520c05413dbf8aa4ed892dbe730a8379de3:
> 
>   github: Upgrade the clang version to 17 (2023-02-02 01:12:17 +0700)
> 
> ----------------------------------------------------------------
> Pull CI updates from Ammar Faizi:
> 
>   Two prep patches to address `-Wextra-semi-stmt` warnings:
> 
>     - Remove unnecessary semicolon (Alviro)
> 
>     - Wrap the CHECK() macro with a do-while statement (Alviro)
> 
>   A patch for the CI:
> 
>     - Upgrade the clang version to 17 and append -Wextra-semi-stmt (me)

Pulled, thanks.

-- 
Jens Axboe



      reply	other threads:[~2023-02-02  3:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 18:30 [GIT PULL] Upgrade to clang-17 (for liburing's CI) Ammar Faizi
2023-02-02  3:09 ` 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] \
    [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