public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Stefan Roesch <[email protected]>
Cc: Facebook Kernel Team <[email protected]>,
	io-uring Mailing List <[email protected]>,
	Jens Axboe <[email protected]>
Subject: Re: [PATCH v6 3/4] liburing: add example programs for napi busy poll
Date: Sat, 4 Feb 2023 04:20:17 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Fri, Feb 03, 2023 at 01:14:30PM -0800, Stefan Roesch wrote:
> Do you happen to know which compiler and what settings are used in the
> CI environment? I don't see these warnings in my local environment.

GCC and Clang, both are not happy. Here is the build result of your
patch series:

   https://github.com/ammarfaizi2/liburing/actions/runs/4087640126/jobs/7048391772

liburing's upstream CI config file can be found here:

   https://github.com/axboe/liburing/blob/master/.github/workflows/build.yml

-- 
Ammar Faizi


  reply	other threads:[~2023-02-03 21:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 19:03 [PATCH v6 0/4] liburing: add api for napi busy poll Stefan Roesch
2023-02-03 19:03 ` [PATCH v6 1/4] liburing: add api to set napi busy poll settings Stefan Roesch
2023-02-03 20:19   ` Ammar Faizi
2023-02-03 21:06     ` Stefan Roesch
2023-02-03 19:03 ` [PATCH v6 2/4] liburing: add documentation for new napi busy polling Stefan Roesch
2023-02-03 19:03 ` [PATCH v6 3/4] liburing: add example programs for napi busy poll Stefan Roesch
2023-02-03 20:43   ` Ammar Faizi
2023-02-03 21:14     ` Stefan Roesch
2023-02-03 21:20       ` Ammar Faizi [this message]
2023-02-03 19:03 ` [PATCH v6 4/4] liburing: update changelog with new feature Stefan Roesch

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