From: DJ Delorie <dj@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha@sourceware.org, carlos@redhat.com, fweimer@redhat.com
Subject: Re: [PATCH v3] x86-64: Add glibc.cpu.prefer_map_32bit_exec [BZ #28656]
Date: Wed, 22 Feb 2023 22:43:56 -0500 [thread overview]
Message-ID: <xnfsax82rn.fsf@greed.delorie.com> (raw)
In-Reply-To: <20230221215259.86835-1-hjl.tools@gmail.com>
"H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org> writes:
> +When this tunable is set to \code{1}, shared libraries of non-setuid
./tunables.texi:592: misplaced {
./tunables.texi:592: misplaced }
Should that be @code{1} ?
next prev parent reply other threads:[~2023-02-23 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 21:52 H.J. Lu
2023-02-22 15:02 ` Carlos O'Donell
2023-02-23 3:43 ` DJ Delorie [this message]
2023-02-23 4:08 ` [PATCH] tunables.texi: Change \code{1} to @code{1} H.J. Lu
2023-02-23 4:23 ` DJ Delorie
2023-02-23 9:01 ` Andreas Schwab
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=xnfsax82rn.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=carlos@redhat.com \
--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).