From: Paul Eggert <eggert@cs.ucla.edu>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] dlfcn: Avoid one-element flexible array in Dl_serinfo
Date: Tue, 18 Jun 2019 15:17:06 -0700 [thread overview]
Message-ID: <8d585f89-e539-e96e-b120-7bd7a788c0b0@cs.ucla.edu> (raw)
In-Reply-To: <87imt37yva.fsf@oldenburg2.str.redhat.com>
That looks OK to me, thanks. (Sorry, I thought I had already said "LGTM".)
next prev parent reply other threads:[~2019-06-18 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 15:37 [PATCH] dlfcn: Avoid one-element flexible array in Dl_serinfo Florian Weimer
2019-06-18 14:27 ` Florian Weimer
2019-06-18 22:17 ` Paul Eggert [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-23 9:34 Florian Weimer
2019-05-23 22:42 ` Paul Eggert
2019-05-23 22:50 ` Joseph Myers
2019-05-24 8:42 ` Florian Weimer
2019-05-24 23:47 ` Paul Eggert
2019-05-27 19:04 ` Florian Weimer
2019-06-01 8:48 ` Paul Eggert
2019-06-03 7:59 ` Florian Weimer
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8d585f89-e539-e96e-b120-7bd7a788c0b0@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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).