public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Pavel Begunkov <[email protected]>,
	io-uring Mailing List <[email protected]>,
	Linux Kernel Mailing List <[email protected]>,
	Ammar Faizi <[email protected]>
Subject: [PATCH liburing v1 0/3] Small fixes and CI update
Date: Wed,  8 Mar 2023 03:38:27 +0700	[thread overview]
Message-ID: <[email protected]> (raw)

Just a boring patchset.

- Address the recent io_uring-udp bug report on GitHub.
- No more sign-compare warnings on the GitHub build bot.
- Kill trailing whitespaces (manpage).

Signed-off-by: Ammar Faizi <[email protected]>
---

Ammar Faizi (3):
  io_uring-udp: Fix the wrong `inet_ntop()` argument
  github: Append `-Wno-sign-compare` to the GitHub build bot CFLAGS
  man/io_uring_register_{buffers,files}: Kill trailing whitespaces

 .github/workflows/build.yml     |  2 +-
 examples/io_uring-udp.c         |  2 +-
 man/io_uring_register_buffers.3 | 10 +++++-----
 man/io_uring_register_files.3   | 22 +++++++++++-----------
 4 files changed, 18 insertions(+), 18 deletions(-)


base-commit: 0dd82f0c63d468c5b3d9510af642968ce6e8ee21
-- 
Ammar Faizi


             reply	other threads:[~2023-03-07 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 20:38 Ammar Faizi [this message]
2023-03-07 20:38 ` [PATCH liburing v1 1/3] io_uring-udp: Fix the wrong `inet_ntop()` argument Ammar Faizi
2023-03-07 20:38 ` [PATCH liburing v1 2/3] github: Append `-Wno-sign-compare` to the GitHub build bot CFLAGS Ammar Faizi
2023-03-07 20:38 ` [PATCH liburing v1 3/3] man/io_uring_register_{buffers,files}: Kill trailing whitespaces Ammar Faizi
2023-03-07 20:55 ` [PATCH liburing v1 0/3] Small fixes and CI update Jens Axboe

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