public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Cc: carlos@redhat.com
Subject: Re: [PATCH 1/4] Add framework for tunables
Date: Sat, 31 Dec 2016 19:50:00 -0000	[thread overview]
Message-ID: <ecfb268d-f850-cca5-d9b6-feb0c1767ab5@sourceware.org> (raw)
In-Reply-To: <e0d00f21-d3fe-7134-1e7c-eaf2d3743b3d@redhat.com>

On Sunday 01 January 2017 01:13 AM, Florian Weimer wrote:
> I missed the __attribute_unused syntax error. :(

Ugh, sorry, that was a stupid mistake.

> I'll fix that shortly.

Thanks.

> I've also realized that the suggested csu/ move
> did not happen, so building with stack protector enabled could be broken.

I saw your comment about it but did not link it to an actual suggestion.
 Did you suggest moving tunables to csu or specific bits of it?

Siddhesh

  reply	other threads:[~2016-12-31 19:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-31 15:41 [PATCH v8 0/4] glibc tunables Siddhesh Poyarekar
2016-12-31 15:41 ` [PATCH 3/4] Enhance --enable-tunables to select tunables frontend at build time Siddhesh Poyarekar
2016-12-31 15:41 ` [PATCH 2/4] Initialize tunable list with the GLIBC_TUNABLES environment variable Siddhesh Poyarekar
2016-12-31 15:45   ` Florian Weimer
2016-12-31 15:50     ` Siddhesh Poyarekar
2016-12-31 15:55       ` Siddhesh Poyarekar
2016-12-31 16:41         ` Florian Weimer
2016-12-31 15:41 ` [PATCH 4/4] User manual documentation for tunables Siddhesh Poyarekar
     [not found] ` <1483198831-2232-2-git-send-email-siddhesh@sourceware.org>
2016-12-31 16:49   ` [PATCH 1/4] Add framework " Florian Weimer
2016-12-31 17:58     ` Siddhesh Poyarekar
2016-12-31 19:43       ` Florian Weimer
2016-12-31 19:50         ` Siddhesh Poyarekar [this message]
2016-12-31 19:52           ` Florian Weimer
2017-01-01 13:40             ` Nix
  -- strict thread matches above, loose matches on Subject: below --
2016-12-30  4:09 [PATCH v7 0/4] glibc tunables Siddhesh Poyarekar
2016-12-30  4:09 ` [PATCH 1/4] Add framework for tunables Siddhesh Poyarekar
2017-02-06 22:36   ` Andreas Schwab
2017-02-07  6:49     ` Siddhesh Poyarekar
2017-02-07 16:06       ` Andreas Schwab
2017-02-08  8:48         ` Siddhesh Poyarekar
2017-02-06 22:59   ` Andreas Schwab
2016-11-16  8:35 [PATCHv6 0/4] glibc tunables Siddhesh Poyarekar
2016-11-16  8:35 ` [PATCH 1/4] Add framework for tunables Siddhesh Poyarekar
2016-12-27 11:08   ` Florian Weimer
2016-12-27 20:59     ` Siddhesh Poyarekar
2016-12-27 21:12       ` Florian Weimer
2016-12-27 21:25         ` Siddhesh Poyarekar
2016-12-30 13:28     ` Joseph Myers
2016-12-31 13:48       ` 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=ecfb268d-f850-cca5-d9b6-feb0c1767ab5@sourceware.org \
    --to=siddhesh@sourceware.org \
    --cc=carlos@redhat.com \
    --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).