GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Pavel Begunkov <[email protected]>,
	Alviro Iskandar Setiawan <[email protected]>,
	io-uring Mailing List <[email protected]>,
	Linux Kernel Mailing List <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>
Subject: Re: [PATCH liburing 0/3] io_uring-udp fix, manpage fix, and hppa cross-compiler
Date: Sat, 15 Apr 2023 14:37:07 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 4/15/23 10:59 AM, Ammar Faizi wrote:
> Hi Jens,
> 
> There are three patches in this series:
> 
> 1. Fix the wrong IPv6 address in io_uring-udp (me).
> 
> Before:
> 
>     port bound to 49567
>     received 4 bytes 28 from ::2400:6180:0:d1:0:0:47048
>     received 4 bytes 28 from ::2400:6180:0:d1:0:0:54755
>     received 4 bytes 28 from ::2400:6180:0:d1:0:0:57968
> 
> (the IPv6 address is wrong)
> 
> After:
> 
>     port bound to 48033
>     received 4 bytes 28 from [2400:6180:0:d1::6a4:a00f]:40456
>     received 4 bytes 28 from [2400:6180:0:d1::6a4:a00f]:50306
>     received 4 bytes 28 from [2400:6180:0:d1::6a4:a00f]:52291
> 
> 2. io_uring_cqe_get_data() manpage fix (me).
> 
> The return value of io_uring_cqe_get_data() will be undefined if the
> user_data is not set from the SQE side.
> 
> 3. Add hppa cross-compiler to the CI (Alviro).

Applied, thanks.

-- 
Jens Axboe



      parent reply	other threads:[~2023-04-15 20:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-15 16:59 [PATCH liburing 0/3] io_uring-udp fix, manpage fix, and hppa cross-compiler Ammar Faizi
2023-04-15 16:59 ` [PATCH liburing 1/3] io_uring-udp: Fix the wrong IPv6 binary to string conversion Ammar Faizi
2023-04-15 16:59 ` [PATCH liburing 2/3] github: Add hppa cross compiler Ammar Faizi
2023-04-15 16:59 ` [PATCH liburing 3/3] man/io_uring_cqe_get_data.3: Fix a misleading return value Ammar Faizi
2023-04-15 20:37 ` 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] \
    [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