From: Andreas Schwab <schwab@linux-m68k.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH] ld.so: Unset glibc tunables for --list-tunables test
Date: Tue, 02 Feb 2021 19:07:37 +0100 [thread overview]
Message-ID: <87lfc6tkba.fsf@igel.home> (raw)
In-Reply-To: <CAMe9rOph540jV_QRn=P6p=RkKmE5hUUMMVWiAAuheJSse18n_A@mail.gmail.com> (H. J. Lu's message of "Tue, 2 Feb 2021 09:36:05 -0800")
On Feb 02 2021, H.J. Lu wrote:
> From 321acb682702dd6ee273207b7ce832f8133abbfa Mon Sep 17 00:00:00 2001
> From: "H.J. Lu" <hjl.tools@gmail.com>
> Date: Tue, 2 Feb 2021 09:31:56 -0800
> Subject: [PATCH] ld.so: Unset glibc tunables for --list-tunables test
>
> Unset glibc tunables and their aliases for --list-tunables test.
Ok. I think the subject should use tst-rtld-list-tunables.sh as the
topic prefix, since it doesn't change ld.so.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-02-02 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 15:44 V4 [PATCH 0/2] ld.so: Add --list-tunables to print tunable values H.J. Lu
2020-10-31 15:44 ` V4 [PATCH 1/2] x86: Move x86 processor cache info to cpu_features H.J. Lu
2021-01-14 14:13 ` Adhemerval Zanella
2021-01-14 19:28 ` V5 " H.J. Lu
2020-10-31 15:44 ` V4 [PATCH 2/2] ld.so: Add --list-tunables to print tunable values H.J. Lu
2021-01-14 18:35 ` Adhemerval Zanella
2021-01-14 22:25 ` V5 " H.J. Lu
2021-01-15 12:47 ` Adhemerval Zanella
2021-02-02 10:59 ` Andreas Schwab
2021-02-02 17:36 ` [PATCH] ld.so: Unset glibc tunables for --list-tunables test H.J. Lu
2021-02-02 18:07 ` Andreas Schwab [this message]
2021-02-02 18:12 ` [PATCH] tst-rtld-list-tunables.sh: Unset glibc tunables H.J. Lu
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=87lfc6tkba.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.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).