From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 1/6] Static inline functions for mallopt helpers
Date: Thu, 27 Oct 2016 03:12:00 -0000 [thread overview]
Message-ID: <35f2c517-1414-9a17-6c65-fb3405c9c79d@sourceware.org> (raw)
In-Reply-To: <xnoa27ov6c.fsf@greed.delorie.com>
On Wednesday 26 October 2016 11:21 PM, DJ Delorie wrote:
>
> - /* Forbid setting the threshold too high. */
>
> This comment got lost.
>
> It would be nice if the functions were in the same order as the cases in
> the switch statement.
>
> Otherwise OK.
Thanks, I've fixed both points and pushed this patch.
Siddhesh
next prev parent reply other threads:[~2016-10-27 3:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 14:43 [PATCH v5 0/6] glibc tunables Siddhesh Poyarekar
2016-10-24 14:43 ` [PATCH 4/6] Initialize tunable list with the GLIBC_TUNABLES environment variable Siddhesh Poyarekar
2016-10-24 15:01 ` Andreas Schwab
2016-10-26 9:48 ` Siddhesh Poyarekar
2016-10-24 14:43 ` [PATCH 2/6] New internal function __access_noerrno Siddhesh Poyarekar
2016-11-08 17:10 ` Adhemerval Zanella
2016-11-08 19:00 ` Siddhesh Poyarekar
2016-11-10 5:47 ` Siddhesh Poyarekar
2016-11-10 12:15 ` Adhemerval Zanella
2016-11-10 13:05 ` Siddhesh Poyarekar
2016-11-10 16:07 ` Adhemerval Zanella
2016-10-24 14:43 ` [PATCH 6/6] User manual documentation for tunables Siddhesh Poyarekar
2016-10-24 17:22 ` Joseph Myers
2016-10-26 9:53 ` Siddhesh Poyarekar
2016-10-24 14:43 ` [PATCH 5/6] Enhance --enable-tunables to select tunables frontend at build time Siddhesh Poyarekar
2016-10-24 14:43 ` [PATCH 3/6] Add framework for tunables Siddhesh Poyarekar
2016-10-24 14:43 ` [PATCH 1/6] Static inline functions for mallopt helpers Siddhesh Poyarekar
2016-10-26 17:51 ` DJ Delorie
2016-10-27 3:12 ` Siddhesh Poyarekar [this message]
2016-11-03 10:26 ` [PING][PATCH v5 0/6] glibc tunables Siddhesh Poyarekar
2016-11-08 5:37 ` [PING 2][PATCH " Siddhesh Poyarekar
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=35f2c517-1414-9a17-6c65-fb3405c9c79d@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=dj@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).