From: Eric Blake <eblake@redhat.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, "Alejandro Colomar" <alx@kernel.org>,
"Bastien Roucariès" <rouca@debian.org>,
glibc <libc-alpha@sourceware.org>, GCC <gcc@gcc.gnu.org>,
"Stefan Puiu" <stefan.puiu@gmail.com>,
"Igor Sysoev" <igor@sysoev.ru>, "Rich Felker" <dalias@libc.org>,
"Andrew Clayton" <andrew@digital-domain.net>,
"Richard Biener" <richard.guenther@gmail.com>,
"Zack Weinberg" <zack@owlfolio.org>,
"Florian Weimer" <fweimer@redhat.com>,
"Joseph Myers" <joseph@codesourcery.com>,
"Jakub Jelinek" <jakub@redhat.com>, "Sam James" <sam@gentoo.org>
Subject: Re: [PATCH v3] sockaddr.3type: POSIX Issue 8 will solve strict-aliasing issues with these types
Date: Fri, 21 Apr 2023 15:35:05 -0500 [thread overview]
Message-ID: <wtqulp3dbbnru6656ne77uv3o7uc7o4zu74ldh7ddsyb35eqt2@oqar2pfrng7d> (raw)
In-Reply-To: <20230421202718.21831-1-alx@kernel.org>
On Fri, Apr 21, 2023 at 10:27:18PM +0200, Alejandro Colomar wrote:
> Link: <https://austingroupbugs.net/view.php?id=1641>
> Reported-by: Bastien Roucariès <rouca@debian.org>
> Reported-by: Alejandro Colomar <alx@kernel.org>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Cc: glibc <libc-alpha@sourceware.org>
> Cc: GCC <gcc@gcc.gnu.org>
> Cc: Stefan Puiu <stefan.puiu@gmail.com>
> Cc: Igor Sysoev <igor@sysoev.ru>
> Cc: Rich Felker <dalias@libc.org>
> Cc: Andrew Clayton <andrew@digital-domain.net>
> Cc: Richard Biener <richard.guenther@gmail.com>
> Cc: Zack Weinberg <zack@owlfolio.org>
> Cc: Florian Weimer <fweimer@redhat.com>
> Cc: Joseph Myers <joseph@codesourcery.com>
> Cc: Jakub Jelinek <jakub@redhat.com>
> Cc: Sam James <sam@gentoo.org>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
> ---
>
> Hi Eric,
>
> I took your informal review as a "Reviewed-by". Please confirm.
> I've also modified the small wording thingy you suggested.
For the avoidance of doubt ;)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2023-04-21 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 17:13 [PATCH] sockaddr.3type: Document that sockaddr_storage is the API to be used Alejandro Colomar
2023-03-30 19:11 ` Eric Blake
2023-04-05 0:42 ` Alejandro Colomar
2023-04-06 16:24 ` Eric Blake
2023-04-06 16:31 ` Alejandro Colomar
[not found] ` <6fdadcff-95a2-44fe-9453-d0200822e01e@app.fastmail.com>
[not found] ` <cgetryf5sc3cn6p4ssb47pa2nivjw5vughv6pmpc6qykt3y3bd@teqf7o5uapqm>
[not found] ` <bba87d12-77ce-386c-ba85-e20a7a1e4b22@owlfolio.org>
2023-04-21 14:58 ` Alejandro Colomar
2023-04-21 15:00 ` Alejandro Colomar
2023-04-21 15:27 ` Eric Blake
2023-04-21 20:27 ` [PATCH v3] sockaddr.3type: POSIX Issue 8 will solve strict-aliasing issues with these types Alejandro Colomar
2023-04-21 20:35 ` Eric Blake [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=wtqulp3dbbnru6656ne77uv3o7uc7o4zu74ldh7ddsyb35eqt2@oqar2pfrng7d \
--to=eblake@redhat.com \
--cc=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=andrew@digital-domain.net \
--cc=dalias@libc.org \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=igor@sysoev.ru \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=richard.guenther@gmail.com \
--cc=rouca@debian.org \
--cc=sam@gentoo.org \
--cc=stefan.puiu@gmail.com \
--cc=zack@owlfolio.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).