From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>,
Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>
Cc: schwab@linux-m68k.org
Subject: Re: [PATCH] Handle DT_UNKNOWN in gconv-modules.d
Date: Wed, 9 Jun 2021 23:58:52 +0530 [thread overview]
Message-ID: <4aca1d23-978f-ab71-82e2-67832f6a7a37@sourceware.org> (raw)
In-Reply-To: <874ke651xa.fsf@oldenburg.str.redhat.com>
On 6/9/21 11:57 PM, Florian Weimer via Libc-alpha wrote:
> * Siddhesh Poyarekar via Libc-alpha:
>
>>> But I think we should move away from alloca, even when we know it
>>> is bounded (sorry if I didn't catch on the previous patch). For
>>> this specific usage we can use asprintf to create the path or use
>>> a static PATH_MAX buffer.
>>
>> I agree, a static PATH_MAX makes sense, I'll do that.
>
> PATH_MAX is not available on Hurd.
(grumbling redacted)
prev parent reply other threads:[~2021-06-09 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 4:38 Siddhesh Poyarekar
2021-06-09 17:21 ` Adhemerval Zanella
2021-06-09 18:08 ` Siddhesh Poyarekar
2021-06-09 18:27 ` Florian Weimer
2021-06-09 18:28 ` Siddhesh Poyarekar [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=4aca1d23-978f-ab71-82e2-67832f6a7a37@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).